If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy all the many features of our fine community. Note that lewd or meaningless nicknames are prohibited (no numbers or letters at random) and please introduce yourself in the section for you to meet our community.
No announcement yet.
Make partitions (boot, kernal, misc, recovery, etc) into a single image?
Hmm. So I've been working on this the past few days and have made progress but a twist is no in the mix. I flashed with N9 firmware no mods. It kinda bricked the device. Then I tried the same thing with Download Android Lollipop 5.1.1 firmware for R-Box Plus - China Gadgets Reviews. This at least got to the boot screen then froze. The main difference was the R-Box had bootload 2.31 and the N9 had an older version. So I added the dumped files from the V88 to the unpacked R-Box. The flashtool (used 'upgrade' and 'restore') said everything went fine (flash, verification, etc) and the device came up. Ok good.
Now here is the interesting part. Made some mods to the working rom. Repacked it. It goes from ~1.3 GB to ~700 MB. I take the 700MB rom and flash it. Device comes up. The strange part though was the apps I removed were still on the device. Then I try changing the wall paper and reflashing. The wall paper is still there.
So the question I'm trying to figure out is why the device is accepting the flash then not doing anything? Any ideas?
I used the misc files that I dumped from the original hardware.
I've been playing around with it more. I think what was happening was that my first img that I thought was working wasn't actually. I used another program and it said it was corrupted. So my current working hypothesis is that when I flashed the img that I though was working, it somehow reverted to the recovery of the img that was nativity on the hardware.
The other things that I'm trying to figure out:
1. Did I use the right bootloader? In the img I made I used 2.31. However, I don't know if that was on the stock firmware because I never dumped it. Is there a way to figure out the bootloader that is on a device?
2. When I unpacked the MRX pro there is a file called boot.bin outside of where other dumped images (boot, kernal, ..) are and I don't know if that is important.
The misc file tells the device what to do on next boot. If you used the one you pulled it won't format data and anything that was previously on the box will still be there. If you use the misc from stock it will format and give you a fresh install.