Q&A for [MOD][OCT 21] MultiROM v29
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD][OCT 21] MultiROM v29. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
recovery issue!
I'm facing a weird issue! When i try to flash an android l preview based rom as a primary rom,it gets stuck at formatting systems!...its fine with kitkat roms! i can't solve this! please help me !
Hi, I have android l preview has secondary rom and I would like to know how to root it or flash a .zip for it. Thank you!
If I flash any .zip file by recovery. In which rom it will be installed? is it primary rom or secondary?
Riyad Pradhan said:
If I flash any .zip file by recovery. In which rom it will be installed? is it primary rom or secondary?
Click to expand...
Click to collapse
If you use the Install, Backup or Wipe options when you first get to recovery are your internal (primary) rom.
All secondary roms are located in Multirom/manage roms/
Please help me.
I installed multirom from the appstore, (rooted my phone before) - then pressed install there - phone rebooted into twrp and then rebooted again. and then it was stuck into the booting screen or how you call it (1+1 logo without any animation). what should i do now? how do i get this fixed? i need my phone back!
memylo said:
I installed multirom from the appstore, (rooted my phone before) - then pressed install there - phone rebooted into twrp and then rebooted again. and then it was stuck into the booting screen or how you call it (1+1 logo without any animation). what should i do now? how do i get this fixed? i need my phone back!
Click to expand...
Click to collapse
Strange, I would try restoring your nandroid and flashing a patched kernel and MultiRom in recovery.
thereal_bigjake said:
Strange, I would try restoring your nandroid and flashing a patched kernel and MultiRom in recovery.
Click to expand...
Click to collapse
Can you explain me how to do this stuff? I installed a uninstall zip for multirom and did a factory reset and was able to install paranoid android, but i want to go back to the stock cm11s. The rom provided by Cynogenmod gives me a error with invladid meta inf.
memylo said:
Can you explain me how to do this stuff? I installed a uninstall zip for multirom and did a factory reset and was able to install paranoid android, but i want to go back to the stock cm11s. The rom provided by Cynogenmod gives me a error with invladid meta inf.
Click to expand...
Click to collapse
First make sure your bootloader and radio are up to date.
Regarding Tassadr's recovery flashable zips, I have one question: what will happen with google OTA updates? Since the recovery is not overwritten, I assume they wouldn't exactly work as usual. Any insight or precautions I should take?
So, these factory image zips don't have a recovery? And won't wipe my data/sdcard correct? So I 'should' be able to dirty flash over the dev preview. Or if not, I will at least still have my custom recovery to restore a nandroid?
So I flashed the lollipop stock rom, threw on super su and francos kernel as secondary rom, but I cannot connect to wifi. Any idea how to fix wifi?
The problem seems to be related to DHCP. I clicked on the advanced option and entered a static IP instead of DHCP and I was able to connect.
Why I can't see multirom boot menu? I press and hold volume up or down but nothing, why?
TWRP Splash
I'm trying to replace the curtain on team win. ive done it before on a different device (no multirom) by unpacking it with (http://www.techknow.me/forum/index.php?topic=6816.0) replacing the curtain.jpg with my custom one, repacking with the same program, and then flashing through flashify. (twrp manager didnt work. no idea why. and the phone couldnt fastboot flash so i couldnt test that, but flashify worked and it replaced the curtain perfectly). my nexus 5 w/ multirom recovery doesnt work though. unpack works. changing curtain works. repack works. but no method of flashing it works. no matter how i flash it, i dont seem to have a recovery. (booting to recovery sticks me at the google screen with the padlock) does anyone have success replacing the curtain or have any clue what im doing wrong? or if its possible?
MistaEast said:
I'm trying to replace the curtain on team win. ive done it before on a different device (no multirom) by unpacking it with (http://www.techknow.me/forum/index.php?topic=6816.0) replacing the curtain.jpg with my custom one, repacking with the same program, and then flashing through flashify. (twrp manager didnt work. no idea why. and the phone couldnt fastboot flash so i couldnt test that, but flashify worked and it replaced the curtain perfectly). my nexus 5 w/ multirom recovery doesnt work though. unpack works. changing curtain works. repack works. but no method of flashing it works. no matter how i flash it, i dont seem to have a recovery. (booting to recovery sticks me at the google screen with the padlock) does anyone have success replacing the curtain or have any clue what im doing wrong? or if its possible?
Click to expand...
Click to collapse
I followed this guide and everything worked the first try. I've repacked quite a few now with no problems.
http://goo.gl/EWw71q
Bonus: you can flash recovery with the Material twrp theme.
I couldnt get android kitchen working this way. Idk what i did wrong but it wasnt unpacking the file at all. So i found a work around with the program i linked to. You just unpacked, replaced, repacked, and flashed the multirom recovery and it worked?
MistaEast said:
I couldnt get android kitchen working this way. Idk what i did wrong but it wasnt unpacking the file at all. So i found a work around with the program i linked to. You just unpacked, replaced, repacked, and flashed the multirom recovery and it worked?
Click to expand...
Click to collapse
Yep works no problem. I was able to use that method on Linux Mint and right on my Nexus 5.
Last question, Did u do it on a windows machine as well? I know Kitchen is a lot easier to install/works better on linux.
MistaEast said:
Last question, Did u do it on a windows machine as well? I know Kitchen is a lot easier to install/works better on linux.
Click to expand...
Click to collapse
No, I don't use Windows at all.
Related
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
mattberman said:
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
Click to expand...
Click to collapse
Look, there's obviously something else going on with your Xoom that is not related to the Honeycomb version you have updated to. My suggestion is to very logically figure out what may have happened to get you stuck so we can get you unstuck.
Of course, if you go to the Moto Dev site you can download the stock images for your Xoom model (be careful to choose the correct model) and flash them through fastboot.
Don't relock.
You can reroot at HC3.01 or you can OTA update to 3.1/3.2 as desired and then root.
It's all up to you.
I know there's something else wrong, but for the life of me I cannot figure out what it is. I've tried different kernels (stock, Tiamat, different branches of each), but whenever I try to build and flash a new kernel, I get stuck at the Motorola logo, and have to reboot and reflash the older rootboot.img from these forums. I tried different mkbootimg offsets (it should be 0xe19f8000 for the Xoom I believe, correct?) and different ramdisks, but still the same problem. Unless there is some other special step I missed for building Xoom kernels, I'm out of ideas, and I know I had better luck building and flashing kernels on Android 3.0.1, so this is sort of my final fallback method.
These are the steps I took to get where I am:
1. Upgrade Android 3.2 OTA (build HTJ85B) for US WiFi Xoom (which is my model)
2. Unlock Xoom via fastboot
3. Copy su files over for root access
4. Build 2.6.36.3 kernel from source tree (many different branches, etc like mentioned above)
5. Extract ramdisk and combine with zImage kernel output using mkbootimg (tried both no offset and offset=0xe19f8000, which I found after digging around on the Xoom)
6. Flash new boot image via fastboot and reboot. This is when I get stuck a Motorola logo..
Any advice?
mattberman said:
I know there's something else wrong, but for the life of me I cannot figure out what it is. I've tried different kernels (stock, Tiamat, different branches of each), but whenever I try to build and flash a new kernel, I get stuck at the Motorola logo, and have to reboot and reflash the older rootboot.img from these forums. I tried different mkbootimg offsets (it should be 0xe19f8000 for the Xoom I believe, correct?) and different ramdisks, but still the same problem. Unless there is some other special step I missed for building Xoom kernels, I'm out of ideas, and I know I had better luck building and flashing kernels on Android 3.0.1, so this is sort of my final fallback method.
These are the steps I took to get where I am:
1. Upgrade Android 3.2 OTA (build HTJ85B) for US WiFi Xoom (which is my model)
2. Unlock Xoom via fastboot
3. Copy su files over for root access
4. Build 2.6.36.3 kernel from source tree (many different branches, etc like mentioned above)
5. Extract ramdisk and combine with zImage kernel output using mkbootimg (tried both no offset and offset=0xe19f8000, which I found after digging around on the Xoom)
6. Flash new boot image via fastboot and reboot. This is when I get stuck a Motorola logo..
Any advice?
Click to expand...
Click to collapse
Quick question: are you using CWM Recovery to flash the zip files, and if so what version of recovery do you have installed?
The version which works best for the Xoom is v3.2.0.0 R4c. However if you "updated" through Rom Manager to v4.0.0.X, that version is incompatible with the external sdcard and if you are trying to flash from your internal sdcard, it will seem like it's working but will not work, will just hang or revert to previous state. So maybe I'm really off base...you seem to know a lot...but I've seen similar problems caused by that bad recovery version.
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
mattberman said:
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
Click to expand...
Click to collapse
So you are decomposing the zip files and flashing image files through fastboot? Because you know you can't flash zip files through fastboot.
mattberman said:
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
Click to expand...
Click to collapse
Worst logic EVAR
mattberman said:
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
Click to expand...
Click to collapse
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
rockhumper said:
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
Click to expand...
Click to collapse
He doesn't have his microsd card yet. But might as well get ready.
okantomi said:
So you are decomposing the zip files and flashing image files through fastboot? Because you know you can't flash zip files through fastboot.
Click to expand...
Click to collapse
Sorry if I was unclear, I am not using any zip files anywhere in the flashing process, except when dealing with the ramdisk. I've done this many times before with other devices, I'm not completely new to the process.
rockhumper said:
Worst logic EVAR
Click to expand...
Click to collapse
How is that bad logic? If something isn't working as it should, go back to the last stable point when it did.
rockhumper said:
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
Click to expand...
Click to collapse
I could try this but how would that help? Do I need a custom recovery image to flash a new kernel? It won't work with stock? I'll give it a shot, thanks for the input. Okantomi, he's talking about the recovery .img file (flashed via fastboot), and not the .zip via CWM (I think).
Just get a 2gb or 4gb sd card, or borrow one from a phone, it's pretty simple...
To go back just grab the stock images from my sticky. Fastboot flash them, wipe cache and start over.
Sent from my PG86100 using Tapatalk
Hi eveyone, I updated my stock from 4.0 to 4.1 through odin and it was really painless. Sorry if this sounds lazy but can you install cm the same way? Doing the whole CW etc. seems a lot of steps - i'd rather upload one file only if possible. Thanks!
Guiyoforward said:
Hi eveyone, I updated my stock from 4.0 to 4.1 through odin and it was really painless. Sorry if this sounds lazy but can you install cm the same way? Doing the whole CW etc. seems a lot of steps - i'd rather upload one file only if possible. Thanks!
Click to expand...
Click to collapse
i do not think you can install zip with odin
LitD said:
i do not think you can install zip with odin
Click to expand...
Click to collapse
Thanks. You cannot - what I mean is: is CM ever realeased as a TAR-compatible ODIN file?
That can certainly be done. But it's not the norm.
Sent from my SGH-T699 using Tapatalk
James chdset
Nardholio said:
That can certainly be done. But it's not the norm.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thanks Nardholio. I'm obviously missing some important feature CWM offers thatthe "odin process" does not. Is it seamless backup amd restore? Or is it the possibility of adding patches and new stuff - say, gapps on top of CM?
Thanks again!
G.
Deleted because I reposted in the intended thread
Guiyoforward said:
Thanks Nardholio. I'm obviously missing some important feature CWM offers thatthe "odin process" does not. Is it seamless backup amd restore? Or is it the possibility of adding patches and new stuff - say, gapps on top of CM?
Thanks again!
G.
Click to expand...
Click to collapse
CWM offers both of those things as an advantage, yes. You also can use CWM with the Stock image to gain the backup and restore features, amongst others.
And really, if you're already running Stock JB, the process is as simple as:
Place The cm-10.2-XXXXXXXX-NIGHTLY-apexqtmo.zip and gapps zip files on your phone, either on the 'internal' or external SD Card. (This even is optional, as they can be sideloaded if you have adb)
Flash CWM with Odin or Heimdall.
Reboot into recovery
Flash the cm nightly.zip
Flash the gapps.zip
wipe /cache with CWM.
Issue a factory reset with CWM.
Reboot to system.
If you're still on ICS, then you just need to add the steps of flashing the JB-stock-modem.zip and JB-stock-bootloader.zip before flashing the cm-nightly.zip (Turn GPS OFF before flashing these, specifically the modem, just to be on the safe side)
If you perform a backup with CWM before flashing anything, you can restore your stock system as you please.
If you simply want to root your relay, flash an appropriate recovery flashable zip copy of Superuser or SuperSU instead of flashing anything else.
kilr00y, along with providing the JB-stock-modem and JB-stock-bootloader recovery-flashable zip files, also provided a JB-stock-image.zip that can be used to go back to a stock-like system.
CWM allows you for a much greater amount of control over your phone, even when still running a stock image, due to the flexibility of being able to flash new applications directly to the system directories (such as Superuser/SuperSU) without having to have everything be signed by Samsung.
Magamo said:
CWM offers both of those things as an advantage, yes. You also can use CWM with the Stock image to gain the backup and restore features, amongst others.
And really, if you're already running Stock JB, the process is as simple as:
Place The cm-10.2-XXXXXXXX-NIGHTLY-apexqtmo.zip and gapps zip files on your phone, either on the 'internal' or external SD Card. (This even is optional, as they can be sideloaded if you have adb)
Flash CWM with Odin or Heimdall.
Reboot into recovery
Flash the cm nightly.zip
Flash the gapps.zip
wipe /cache with CWM.
Issue a factory reset with CWM.
Reboot to system.
Click to expand...
Click to collapse
THANKS! This is by far the easiest step by step instructions I've seen, and gladly I'm on stock JB already.
Will give this a try
thanks again!
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Guiyoforward said:
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Click to expand...
Click to collapse
In all honesty, ODIN itself is an underdocumented POS, the recovery.img file (or in this case, the renamed apexq_recovery-10.2.img file if you were following along with the wiki) comes right from the build process, it can be flashed directly without much tooling about with it using heimdal, which is an open source replacement for ODIN, that works very well. Heimdall can be used optionally with a GUI, but I personally use it from the command line, to get it to flash a recovery image to the recovery partition of a Relay, it's simply:
heimdall flash --recovery apexq_recovery-10.2.img
Guiyoforward said:
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Click to expand...
Click to collapse
How did you transform the img to md5 (I can also take the cwm in md5 format from the root thread, am I right?) ?
So I can flash anything without root using this method (even recovery) ? I couldn't do this with my desire Z, it's confusing me !
Which recovery should I flash to use cm10.2 (the cwm or the apexq_recovery-10.2.img ?) ?
=> If I use an older recovery I can't flash any jelly been rom's ?
robuser007 said:
(I can also take the cwm in md5 format from the root thread, am I right?)
Click to expand...
Click to collapse
yes, you can
robuser007 said:
So I can flash anything without root using this method (even recovery) ? I couldn't do this with my desire Z, it's confusing me !
Click to expand...
Click to collapse
there are several differences. you can flash recovery via odin to a not rooted device
robuser007 said:
Which recovery should I flash to use cm10.2 (the cwm or the apexq_recovery-10.2.img ?) ?
Click to expand...
Click to collapse
google 'install cyanogenmod samsung relay' and follow 'how to install cyanogenmod for samsung relay' wiki. 'installing cyanogenmod from recovery' is the same as for desire z
Hello guys,
I'm still relatively new to rooting stuff on the Nexus 5 (and 7). Running a rooted stock android 4.4.4. with Franco kernal, but with Lollipop now available.. Of course I want to upgrade. I am looking for a stock android 5 rom with prepoot. Is there a prerooted rom available? And do I have to flash stock kernal first before flashing the rom?
Thanks in advance!
Justin
IVS IVRIS said:
Hello guys,
I'm still relatively new to rooting stuff on the Nexus 5 (and 7). Running a rooted stock android 4.4.4. with Franco kernal, but with Lollipop now available.. Of course I want to upgrade. I am looking for a stock android 5 rom with prepoot. Is there a prerooted rom available? And do I have to flash stock kernal first before flashing the rom?
Thanks in advance!
Justin
Click to expand...
Click to collapse
Not exactly no. L root is different from KitKat. You have to flash a permissive boot.img (kernel) before flashing SuperSU in recovery.
There are flashable zips. There is one linked in the "guides and info" link in my signatrue (see section 6)... But you still need to flash the chainfire or @sykopompos Permissive boot.img
rootSU said:
Not exactly no. L root is different from KitKat. You have to flash a permissive boot.img (kernel) before flashing SuperSU in recovery.
There are flashable zips. There is one linked in the "guides and info" link in my signatrue (see section 6)... But you still need to flash the chainfire or @sykopompos Permissive boot.img
Click to expand...
Click to collapse
Thank you for the quick reply. The rom over here: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 may suit my needs indeed. Although he's saying "-Don't install SuperSU (won't work, must use CF-Auto-Root)"
So, in my situation.. what I should do would be:
Factory reset
Flash rom with TWRP (my recovery)
Flash radio
Use the latest CF-Auto Root (for Lollipop)
Do I keep my Franco kernal?
IVS IVRIS said:
Thank you for the quick reply. The rom over here: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 may suit my needs indeed. Although he's saying "-Don't install SuperSU (won't work, must use CF-Auto-Root)"
So, in my situation.. what I should do would be:
Factory reset
Flash rom with TWRP (my recovery)
Flash radio
Use the latest CF-Auto Root (for Lollipop)
Do I keep my Franco kernal?
Click to expand...
Click to collapse
I wouldn't use CF autoroot myself. Its similar to a toolkit which we don't recommend.
All you do is flash ROM.zip
Flash Permissive boot.img (kernel)
Flash SuperSU (It will work in this case)
I'll see if I can find a link to @sykopompos boot image
No, I don't believe franco will work. I would recommend trying ElementalX though. You flash it after the permissive boot.img. You jeep the permnissive stuff as ElementalX doesn't replace RAMdisk (just modifies it) so you get best of both worlds.
Plus ElementalX is a great kernel. You'll also be running teh same setup as me then
rootSU said:
I wouldn't use CF autoroot myself. Its similar to a toolkit which we don't recommend.
All you do is flash ROM.zip
Flash Permissive boot.img (kernel)
Flash Elemental X kernal
Flash SuperSU (It will work in this case)
I'll see if I can find a link to @sykopompos boot image
No, I don't believe franco will work. I would recommend trying ElementalX though. You flash it after the permissive boot.img. You jeep the permnissive stuff as ElementalX doesn't replace RAMdisk (just modifies it) so you get best of both worlds.
Plus ElementalX is a great kernel. You'll also be running teh same setup as me then
Click to expand...
Click to collapse
Thanks allot for the explanation! Alright, to do:
Put rom on internal memory
Boot into TWRP recovery
Whipe everything, cache, system etc.
Flash the rom
Flash the radio
Flash permissive boot.img
Flash Elemental X kernal
Flash SuperSU
Then reboot
Is that the correct way?
IVS IVRIS said:
Thanks allot for the explanation! Alright, to do:
Put rom on internal memory
Boot into TWRP recovery
Whipe everything, cache, system etc.
Flash the rom
Flash the radio
Flash permissive boot.img
Flash SuperSU
Then reboot
Is that the correct way?
Click to expand...
Click to collapse
Yep, hold on on that, let me source the link.
---------- Post added at 04:33 PM ---------- Previous post was at 04:23 PM ----------
Search the OP of this thread for "modified kernel"
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003
Sorry for bothering.. I think I've got everything setup up.
I've downloaded the files:
bigxie_hammerhead_LRX21O-signed.zip (rom)
LGD820_LRX21O_RADIO.zip (radio)
N5_+LPX13D_ModifiedKernel (modified kernal)
UPDATE-SuperSU-v2.01 (SuperSU)
ElementalX-N5-2.03 (ElementalX)
Is it correct to flash it in this order? Did I get all the steps? The files I have downloaded are partially for L developer (such as SuperSU) preview.. does that matter? I also see reports of sd card not showing up.. any problems ahead?
rootSU said:
Yep, hold on on that, let me source the link.
---------- Post added at 04:33 PM ---------- Previous post was at 04:23 PM ----------
Search the OP of this thread for "modified kernel"
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003
Click to expand...
Click to collapse
Sorry for bothering.. I think I've got everything setup up.
I've downloaded the files:
bigxie_hammerhead_LRX21O-signed.zip (rom)
LGD820_LRX21O_RADIO.zip (radio)
N5_+LPX13D_ModifiedKernel (modified kernal)
ElementalX-N5-2.03 (ElementalX)
UPDATE-SuperSU-v2.01 (SuperSU)
Is it correct to flash it in this order? Did I get all the steps? The files I have downloaded are partially for L developer (such as SuperSU) preview.. does that matter? I also see reports of sd card not showing up.. any problems ahead?
Guys, I got myself in some real trouble I think.
First of all:
I came from 4.4.4. stock rooted with Franco kernal
I did make a backup in TWRP, files are on my pc.
Process:
First of all, I did a factory reset in TWRP
I flashed the rom, radio, kernal for root and supersu.
First boot went fine, although WiFi couldn't be found.
I decided to boot into recovery again to wipe my SD Card
Upon rebooting, phone is looking all black without a real 'launcher', sd card not found etc.
Than:
I managed to push rom, radio, kernal and supersu to /sdcard by adb in rocovery mode
I reflashed all of these, but the same problems occur
What should I do now? I'm ****ting my pants..
IVS IVRIS said:
Guys, I got myself in some real trouble I think.
First of all:
I came from 4.4.4. stock rooted with Franco kernal
I did make a backup in TWRP, files are on my pc.
Process:
First of all, I did a factory reset in TWRP
I flashed the rom, radio, kernal for root and supersu.
First boot went fine, although WiFi couldn't be found.
I decided to boot into recovery again to wipe my SD Card
Upon rebooting, phone is looking all black without a real 'launcher', sd card not found etc.
Than:
I managed to push rom, radio, kernal and supersu to /sdcard by adb in rocovery mode
I reflashed all of these, but the same problems occur
What should I do now? I'm ****ting my pants..
Click to expand...
Click to collapse
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Try updating TWRP to 2.8.1.0. Wipe system/data/cache/dalvik under advanced and then flash the ROM.
Sorry, only way I know how to flash a recovery is with fastboot, no zips...
Or fastboot flash the factory image but do each img separately as I hear there are still issues using the flash.all script when it comes to the system image.
jeky82 said:
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Click to expand...
Click to collapse
Sounds exactly like me indeed. Anyone knows the steps to help us?
galakanokis said:
Try updating TWRP to 2.8.1.0. Wipe system/data/cache/dalvik under advanced and then flash the ROM.
Sorry, only way I know how to flash a recovery is with fastboot, no zips...
Or fastboot flash the factory image but do each img separately as I hear there are still issues using the flash.all script when it comes to the system image.
Click to expand...
Click to collapse
Will this fix the sd card as well?
Are people having the same problem with clockworks recovery mod?
jeky82 said:
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Click to expand...
Click to collapse
I fixed it! Please check this post: http://forum.xda-developers.com/showpost.php?p=56743199&postcount=10 and follow the instructions.. you may have to flash the seperate .img files though, like I had to.
Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?
TWRP is a recovery. A bootloader is a bootloader.
This is covered in every rom thread that updated from L to M.
lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?
Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Install the 3.0.3-0 common TWRP, then try to format data (Wipe ->Format Data-> type yes). Reboot recovery once and then perform a wipe of all partitions (Wipe->Advanced Wipe-> select everything). If you get stuck at "updating partition details..." just wait. It could take as long as five minutes some times to get unstuck.
This is the link for the thread of Slim6, the mm rom I recommend by Andi:
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim6-t3414798/page1
And this is an aosp mm rom also by Andi, try it if above fails
http://builds.unlegacy-android.org/aosp-6.0
Flash both with TWRP 3.0.3-0
If problems continue, post the recovery log (you can find it after reboot at /cache/recovery/ )
landetta said:
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Click to expand...
Click to collapse
have you used the twrp on the http://andi34.github.io/ website? and roms compiled before 3/22/16 dont flash with common twrp when I updated twrp I had downloaded the zip and went into twrp to flash it I havent used a pc at all to install twrp and root . so I just put the zip on my sd card and it updated it did you update twrp with odin?
Thank you for your reply,
Yes I used the recoveries from Android Andi, and yes I have installed recoveries in zip form through recovery and Odin. Unfortunately neither have worked. I did use the latest recoveries when I tried to install the newer roms but it just gets stuck, I can't even make nandroid backups it also gets stuck with the newer recoveries.
Edit:
@ john99ap Sorry i just got home, I tried what you said but it just got stuck at both wipes, I waited 10 mins but a no-go. I found the logs, I couldn't paste them in here because it exceeded character length so I put it in pastebin. I didn't know which log to use so I am giving you the ones that I think are more relevant
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
landetta said:
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
Click to expand...
Click to collapse
I can't find anything in these logs
I need the log in which you try to install the zip file.
Try this:
-Install TWRP 3.0.3-0 (if it's not already there)
-Reboot and delete all recovery logs you can find
-Install the zip without doing anything else before or after so that the log is as clean as possible
-Post any log you find
PS: you could upload logs in your reply by hitting the button with a stapler on the bottom left corner
Thanks for your reply, sorry about the old logs, here are the new ones like you requested. Hopefully you find something in these new ones. Thanks again for all your help BTW I don't have any staples in my advanced reply so I had to use Pastebin again sorry. I think its because of my low post count.
pastebin/UcntGLTZ
pastebin/Fq8V7WUf
PS: Not even the reboot button works on 3.0.3-0.
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
john99ap said:
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
Click to expand...
Click to collapse
Awe thanks anyways dude, I really appreciate you trying. One last thing, on Andi's website he say that device specific 3.0.0-0 recovery should work to flash the latest roms. If anyone can confirm this maybe I can get the new roms working on it. Thanks again for all your help john99ap :good: