Related
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
wrong advice, my mistake... thanks for the reminding simms22.
But I wanna stay rooted
Sent from my Nexus 4 using xda app-developers app
You don't have to unroot. Just download and flash TWRP 2.6.3.2. On that build, they fixed the issues of 4.4 ROMS incorrectly flashing. Using it myself with no problems. Its in Original Android Development if I'm not mistaken
Flashing 4.4 Factory Image issues
Currently on my Nexus 4.
Android 4.3 Unlocked and Rooted
Kernel Version: 3.4.0-perf-gf43c3d9
Build: JWR66Y
Baseband: M9614A-CEFWMAZM-2.0.1700.84
Using ClockWorkMod Recovery v6.0.4.3, when trying to flash the 4.4 factory image .zip file on the SD Card I keep getting an "Installation Aborted" error after "Installing update..." step and the red Triangle on the android figure.
When attempting to sideload using stock recovery, getting a "Signature Verification Failed"
Any Suggestions? Thanks
darkfire2040 said:
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you haven't already tried it, under Mount uncheck system, that solved the problem for me.
Yeah I wanna stay in twrp so I will try flashing the latest. The error I'm getting is. Error while trying to update binarys
Sent from my Nexus 4 using xda app-developers app
will_chrome said:
you've got to unroot and back to stock rwcovery 1st if I'm not mistake. the guide to flash stock rom can be found in http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
wtf??? never ever give advice on android ever again!
op, all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
simms22 said:
all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
Click to expand...
Click to collapse
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
simms22 said:
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
Click to expand...
Click to collapse
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
simms22 said:
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
Click to expand...
Click to collapse
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
na. really the only 100% working fix is to delete the recovery, then reflash.
simms22 said:
na. really the only 100% working fix is to delete the recovery, then reflash.
Click to expand...
Click to collapse
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
ph37rd said:
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
simms22 said:
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
Click to expand...
Click to collapse
OK that confuses me. If using fastboot to place a new boot loader, radio, recovery and ROM are onto the phone and I have to 'fastboot flash recovery recovery.img' to replace the stock recovery that doesn't wipe out the stock recovery? Fabulous sentence structure.
Sent from my Nexus 4 using Tapatalk
Hi,
I've recently installed cwm 6.0.4.4 on my LG G2. It installed pretty flawlessly, and I can flash pretty much any custom ROM... Except the ones running 4.4 or higher. I flashed CM 10.2 and it runs well, but when I try to install CM11, or any other kitkat rom I get this error:
set_metadata_recursive: some changes failed
E: Error in /data/media/0/[Insert name of rom here]
(status 7)
Installation aborted
I get the same error every time, no matter what 4.4 rom I try to flash.
I also tried TWRP (whatever the latest version is) and I also get an error.
Any idea how to fix this frustrating issue?
Thanks
Try redownloading the ROM or a different ROM sounds like a bad download I can't help you much because I have the verizon variant but try doing that and it sounds like you can restore backups so prob just a bad download
I Am NoT responsible for any bricks when you root flash or anything like that hope you get it working
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
Try redownloading the ROM or a different ROM sounds like a bad download I can't help you much because I have the verizon variant but try doing that and it sounds like you can restore backups so prob just a bad download
I Am NoT responsible for any bricks when you root flash or anything like that hope you get it working
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
I tried that, its literally every KitKat ROM I try to flash.
ZombieDawgg said:
I tried that, its literally every KitKat ROM I try to flash.
Click to expand...
Click to collapse
gusly said:
TWRP 2.6.3.2 isn't the latest release, so that might be your problem. Go here: http://forum.xda-developers.com/showthread.php?t=2469995 flash the new zip from your current TWRP, and you should be able to flash KitKat ROMs now. Or, if you prefer CWM, there's PhilZ Touch CWM here http://forum.xda-developers.com/showthread.php?t=2554053
Click to expand...
Click to collapse
This guy had a similar issue. I would say try installing PhilZ Touch CWM for the 802.
Maybe try TWRP.
Its gotta be the recovery.
Sorry I have a VS980, I honestly have issues with TWRP and use the recovery you have.
You could use flashify direct from your device if you hunt down the .IMG.
Give it a shot. BTW not my problem it you brick your phone... I will however try to help you get back up and running.
See my post here
http://forum.xda-developers.com/showthread.php?p=50361473
Sent from my LG-D802 using Tapatalk
Mikkey81 said:
This guy had a similar issue. I would say try installing PhilZ Touch CWM for the 802.
Maybe try TWRP.
Its gotta be the recovery.
Sorry I have a VS980, I honestly have issues with TWRP and use the recovery you have.
You could use flashify direct from your device if you hunt down the .IMG.
Give it a shot. BTW not my problem it you brick your phone... I will however try to help you get back up and running.
Click to expand...
Click to collapse
Thanks, it worked brilliantly!
This is essentially the Nexus 7 2013 WiFi's factory stock image in flashable zip format, so you can flash the device back to factory stock using CWM or TWRP, without having to rely on fastboot. It is useful for people who broke their USB port, but still have custom recovery. Or messing with roms on the go and wanting to return to stock without having access to a computer.
Included are separate zip files that will flash specific partitions of the device. To have a complete stock form of the device and preventing any issues, make sure you flash all zip files. More advance users can choose to only flash specific partitions to suit their needs.
>>> DOWNLOAD: razor_lrx21p_stock_flashable_zips <<<
Flash instruction (Important):
0. (optional) Create a full nandroid backup before flashing is recommended.
1. To have a working and stable OS, make sure you flash all the zip files, unless you know what you're doing.
2. To prevent serious incompatibilities, do a factory reset if you are coming from KitKat or from a custom rom. I would only skip doing a factory reset if the device is already running stock Lollipop.
Note: If you do not want to erase your custom recovery, do not flash the "recovery.zip", this will return your custom recovery back to stock.
I have tested flashing these multiple times with my Nexus 7 WiFi 32gb with no issues. Before proceeding with flashing, each zip files will check to make sure if the device is a Nexus 7 2013 WiFi (flo), so it won't allow you to accidentally flash on a wrong device.
If you have any issues after flashing these, even after factory resetting, follow this guide to use fastboot instead to return the device to stock.
MD5 Checksum:
File: razor_lrx21p_boot.zip
MD5: 9c12f5f7a83facf80cf596a6de1187ab
File: razor_lrx21p_bootloader_4.04.zip
MD5: 818864adb28b3559fd9d7107115de57c
File: razor_lrx21p_ddr.zip
MD5: d4ee8ae2ec00a37dc9af589cee87f9e0
File: razor_lrx21p_recovery.zip
MD5: 86d2f2d8b784ee108153b0606220040f
File: razor_lrx21p_system.zip
MD5: a0d5c8ce8fbaadc2c304f1f78e9bd6cc
Thanks a lot.
I am currently using Cleanrom. I have download the stock rooted Lolipop, and wish to flash that. It was said in that thread, that I need the latest bootloader. So from the zip file above, should I only flash the bootloader and then flash L? Or would it not make a difference if I flashed all the zips (besides the recovery)?
No, I do not want to get rid of my custom recovery. I am using the latest version of TWRP
Flashed with TWRP, works well. Thanks a lot!
eksasol said:
This is essentially the Nexus 7 2013 WiFi's factory stock image in flashable zip format, so you can flash the device back to factory stock using CWM or TWRP, without having to rely on fastboot. It is useful for people who broke their USB port, but still have custom recovery. Or messing with roms on the go and wanting to return to stock without having access to a computer.
Included are separate zip files that will flash specific partitions of the device. To have a complete stock form of the device and preventing any issues, make sure you flash all zip files. More advance users can choose to only flash specific partitions to suit their needs.
>>> DOWNLOAD: razor_lrx21p_stock_flashable_zips <<<
Flash instruction (Important):
0. (optional) Create a full nandroid backup before flashing is recommended.
1. To have a working and stable OS, make sure you flash all the zip files, unless you know what you're doing.
2. To prevent serious incompatibilities, do a factory reset if you are coming from KitKat or from a custom rom. I would only skip doing a factory reset if the device is already running stock Lollipop.
Note: If you do not want to erase your custom recovery, do not flash the "recovery.zip", this will return your custom recovery back to stock.
I have tested flashing these multiple times with my Nexus 7 WiFi 32gb with no issues. Before proceeding with flashing, each zip files will check to make sure if the device is a Nexus 7 2013 WiFi (flo), so it won't allow you to accidentally flash on a wrong device.
If you have any issues after flashing these, even after factory resetting, follow this guide to use fastboot instead to return the device to stock.
MD5 Checksum:
File: razor_lrx21p_boot.zip
MD5: 9c12f5f7a83facf80cf596a6de1187ab
File: razor_lrx21p_bootloader_4.04.zip
MD5: 818864adb28b3559fd9d7107115de57c
File: razor_lrx21p_ddr.zip
MD5: d4ee8ae2ec00a37dc9af589cee87f9e0
File: razor_lrx21p_recovery.zip
MD5: 86d2f2d8b784ee108153b0606220040f
File: razor_lrx21p_system.zip
MD5: a0d5c8ce8fbaadc2c304f1f78e9bd6cc
Click to expand...
Click to collapse
Flawless as usual, thanks Eksasol
Great, will do this tomorrow! Thanks
Envoyé de ma Nexus 7.2 depuis tapatalk
particular order?
Thank you very much eksasol!
Is there a particular order in which these files should be flashed?
Cheers,
Sandor
schermvlieger said:
Thank you very much eksasol!
Is there a particular order in which these files should be flashed?
Cheers,
Sandor
Click to expand...
Click to collapse
No they should all work. The phone will boot correctly as long as you have all the proper kernel (boot), system (OS) and bootloader installed.
timrock said:
Thanks a lot.
I am currently using Cleanrom. I have download the stock rooted Lolipop, and wish to flash that. It was said in that thread, that I need the latest bootloader. So from the zip file above, should I only flash the bootloader and then flash L? Or would it not make a difference if I flashed all the zips (besides the recovery)?
No, I do not want to get rid of my custom recovery. I am using the latest version of TWRP
Click to expand...
Click to collapse
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Marvellous!
eksasol said:
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Click to expand...
Click to collapse
Would a factory reset delete the files I have on my device? If so, the ROM is in a folder on my device.
Sent from my Nexus 7 using Tapatalk
Which one of these zips controls user data? I want to try and dirty flash, as I dont want to lose any data if I dont have to. Any suggestions?
I have not done a factory reset yet; and add away tells me the device is not rooted.
Did the update remove root, or is this one of those issues related to not doing a factory reset?
All else seems to be working at the moment.
eksasol said:
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Click to expand...
Click to collapse
So the bootloader and DDR zips can be flashed through TWRP to update the bootloader only, and then a separate rooted ROM (ie scrosler's) can be flashed through TWRP with the help of the updated bootloader?
I did try to flash the bootloader only, but it failed. The need for the DDR would explain why.
Cheers.
Thanks this is what ive been looking for.
Bought my nexus 7 2013 3weeks ago it came with 4.4.2 and i towelrooted it n flashed twrp now on a custom rom but wish i didnt coz i wanted the updates 5.0 but i dont have a pc so this is what i needed.
So if i flash all zips does that mean il be stock 5.0 and ready for future updates?
Aslo my bootloader is already 4.04 so should i stil flash the one above?
Is it possable to flash jus system+boot zips as a second rom (multirom)?
I am not going to install 5.0 yet because some of the apps I use are not yet compatible. If I just flashed the boot loader but stayed with my current ROM , cleanrom, would that be a problem?
Sent from my Nexus 7 using Tapatalk
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
James_Feltham said:
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
Click to expand...
Click to collapse
Hi James,
You'll need to re-root your device after you flashed these images.
CF-Autoroot will help you here; click.
You'll need to reinstall your custom bootloader as well if the stock bootloader does not meet your requirements.
timrock said:
Would a factory reset delete the files I have on my device? If so, the ROM is in a folder on my device.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It depends, for normal Android devices, if you factory reset using stock recovery it will wipe everything in the device. For TWRP and CWM, if you factory reset it will leave your internal storage alone.
MWFD said:
Which one of these zips controls user data? I want to try and dirty flash, as I dont want to lose any data if I dont have to. Any suggestions?
Click to expand...
Click to collapse
None of them control userdata, I excluded that partition image. If you want to dirty flash, just don't do a factory reset or wipe your /data folder.
toonarmy4life said:
Thanks this is what ive been looking for.
Bought my nexus 7 2013 3weeks ago it came with 4.4.2 and i towelrooted it n flashed twrp now on a custom rom but wish i didnt coz i wanted the updates 5.0 but i dont have a pc so this is what i needed.
So if i flash all zips does that mean il be stock 5.0 and ready for future updates?
Aslo my bootloader is already 4.04 so should i stil flash the one above?
Is it possable to flash jus system+boot zips as a second rom (multirom)?
Click to expand...
Click to collapse
Do not flash these zip as a secondary rom for multirom, this is meant to flash for the entire device only. This is factory images, not roms. You could download some type of stock based roms and use it with multirom instead. If you have the latest bootloader you don't need to flash it again, but it won't hurt if you do. Yes, flashing all the zips and factory resetting will return the device to stock.
timrock said:
I am not going to install 5.0 yet because some of the apps I use are not yet compatible. If I just flashed the boot loader but stayed with my current ROM , cleanrom, would that be a problem?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That should not be any problem.
James_Feltham said:
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
Click to expand...
Click to collapse
Because this is Android 5, it have extra security to prevent rooting like in the past. I believe to get root you need try Chainfire's CF-AutoRoot method, or use a custom kernel and flash SuperSu.
schermvlieger said:
I have not done a factory reset yet; and add away tells me the device is not rooted.
Did the update remove root, or is this one of those issues related to not doing a factory reset?
All else seems to be working at the moment.
Click to expand...
Click to collapse
This isn't an update. It is a factory image that return the device to stock form. You will lose root and every changes to the system partition in the process.
Can this file be flashed on any device??
#divy said:
Can this file be flashed on any device??
Click to expand...
Click to collapse
No only on Nexus 7 2013 WiFi 32gb
Okay so i have a few questions here its been a while since i have placed a Rom onto my device the last one was a Sprint model of the G2 and i was able to successfully install CM12 nightly onto it.
With my T-Mobile G2 i had used the once click root application to do so and used auto rec from the app store to install TWRP recovery hopefully i didn't do anything wrong at this point. So now i try to boot into recovery using the power and the down key at the same time but when i did this i was prompted with do you want to reset all data or not and i of course i chose no and booted back home.
Yes i have Super Su with granting access so to solve this minor problem. I had the quick boot application here to boot into recovery but another problem persisted. I cant flash anything over it fails every time and i am trying to flash 5.1.1 cm 12 i think with gapps with 5.1 i believe but in doing so still failed it matched up and everything. I thought that maybe i was trying to flash something that's really not compatible with my phone so i tried to use the same rom but different carriers.
It was cm-12-20150406-NIGHTLY-D801.zip and gapps-lp-20150222-signed but still failed to install the rom? is there something im doing wrong? May i have a tutorial step by step on what to do to successfully flash? and why cant i boot into recovery with the button configuration did i do something wrong with that i just want to so that if theirs a boot load epidermic and i need to use that to restore and see what the problem is? just need help please
Tensaz said:
Okay so i have a few questions here its been a while since i have placed a Rom onto my device the last one was a Sprint model of the G2 and i was able to successfully install CM12 nightly onto it.
With my T-Mobile G2 i had used the once click root application to do so and used auto rec from the app store to install TWRP recovery hopefully i didn't do anything wrong at this point so now i try to boot into recovery using the power and the down key at the same time but when i did this i was prompted with do you want to reset all data or not and i of course i chose no and booted back home and yes i have Super Su with granting access so to solve this minor problem i had the quick boot application here to boot into recovery but another problem persisted i cant flash anything over it fails every time and i am trying to flash 5.1.1 cm 12 i think with gapps with 5.1 i believe but in doing so still failed it matched up and everything. I thought that maybe i was trying to flash something that's really not compatible with my phone so i tried to use the same rom but different carriers cm-12-20150406-NIGHTLY-D801.zip and gapps-lp-20150222-signed but still failed to install the rom? is there something im doing wrong? May i have a tutorial step by step on what to do to successfully flash? and why cant i boot into recovery with the button configuration did i do something wrong with that i just want to so that if theirs a boot load epidermic and i need to use that to restore and see what the problem is? just need help please
Click to expand...
Click to collapse
There's no way anyone can read that without any punctuation marks or any paragraph order.
Basically, the data reset function doesn't work when you have a custom recovery, that's how you enter it. But the TWRP version installed is usually old, somewhat like 2.7.0.0, so you need to update it before installing any roms.
If you really do have recovery installed when you get to the screen about erasing data just choose yes and yes and it will just take you to recovery. If that's too scary for you then just boot into recovery using an app like rebooter from the play store.
As far as flashing it sounds like you may have downloaded bad files. If you're using your phone to download the roms maybe try using a pc then transferring to your phone. And DON'T flash roms for a different carrier, you're just asking for trouble.
Sent from my LG-D801
Choristav said:
There's no way anyone can read that without any punctuation marks or any paragraph order.
Basically, the data reset function doesn't work when you have a custom recovery, that's how you enter it. But the TWRP version installed is usually old, somewhat like 2.7.0.0, so you need to update it before installing any roms.
Click to expand...
Click to collapse
I Have version 2.8.6.1
rick09 said:
If you really do have recovery installed when you get to the screen about erasing data just choose yes and yes and it will just take you to recovery. If that's too scary for you then just boot into recovery using an app like rebooter from the play store.
As far as flashing it sounds like you may have downloaded bad files. If you're using your phone to download the roms maybe try using a pc then transferring to your phone. And DON'T flash roms for a different carrier, you're just asking for trouble.
Sent from my LG-D801
Click to expand...
Click to collapse
I used my computer to download the files all together and the problem still persisted.
And that i do know to not flash with different Carrier did it with a s4 without thinking.
Tensaz said:
I used my computer to download the files all together and the problem still persisted.
And that i do know to not flash with different Carrier did it with a s4 without thinking.
Click to expand...
Click to collapse
The problem might be that you are on the wrong bootloader so v30 lollipop. As loki and bump don't work on it it will result into an failed flash. What you can do is flash the right bootloader or easily downgrade bootloader and bootstack with autorec for your phone. Read carefully which one you need for your tmobile d801. If there is an loki error then just flash the jellybean bootloader what you easily can do with autorec.
Sent from my LG-D802 using Tapatalk
wulsic said:
The problem might be that you are on the wrong bootloader so v30 lollipop. As loki and bump don't work on it it will result into an failed flash. What you can do is flash the right bootloader or easily downgrade bootloader and bootstack with autorec for your phone. Read carefully which one you need for your tmobile d801. If there is an loki error then just flash the jellybean bootloader what you easily can do with autorec.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Still a bit noobish how do i do that boot loader thing?
Tensaz said:
Still a bit noobish how do i do that boot loader thing?
Click to expand...
Click to collapse
Well you download the right version for your d801
https://www.androidfilehost.com/?w=files&flid=13763
Then you need to install it
Click on the lollipop and let it do its job. If it asks for root then allow it.
It will probably reboot and you are done. Only need to flash then a newer recovery. Also search bender_007 on xda and leave him a thanks perhaps for his app
Sent from my LG-D802 using Tapatalk
wulsic said:
Well you download the right version for your d801
Then you need to install it
Click on the lollipop and let it do its job. If it asks for root then allow it.
It will probably reboot and you are done. Only need to flash then a newer recovery. Also search bender_007 on xda and leave him a thanks perhaps for his app
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
my god i can flash now awesome thank you now i have one last question if you dont mind telling me since i downgraded my boot loader to kk i think using the auto rec do i need to flash my current 30b boot-stack first before i use my stock restore? or is there an easier way to do so (tried to go into stock but was met with a black screen after lg logo)
Tensaz said:
my god i can flash now awesome thank you now i have one last question if you dont mind telling me since i downgraded my boot loader to kk i think using the auto rec do i need to flash my current 30b boot-stack first before i use my stock restore? or is there an easier way to do so (tried to go into stock but was met with a black screen after lg logo)
Click to expand...
Click to collapse
Well, as far as I know autorec downgrades to jb bootloader, to boot into stock you could find d801 lp modem and d801 lp bootstack/bootloader as it might need kk bootloader
Sent from my LG-D802 using Tapatalk
wulsic said:
Well, as far as I know autorec downgrades to jb bootloader, to boot into stock you could find d801 lp modem and d801 lp bootstack/bootloader as it might need kk bootloader
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thank you for your help i now have a boot loader for stock that i found and im using auto rec for every time i reboot to cm12 getting the hang of this flashing thing i just want to know if theres any problems with the network service for cm12 at all?
Tensaz said:
thank you for your help i now have a boot loader for stock that i found and im using auto rec for every time i reboot to cm12 getting the hang of this flashing thing i just want to know if theres any problems with the network service for cm12 at all?
Click to expand...
Click to collapse
With cm12 I am not sure but the cause could be perhaps the wrong modem, and or bootloader. I also suggest to check out newer custom roms the only cyanogenmod as some custom roms are already running on lollipop modem and caf. CAF is code aurora forum so kinda it will also have changes specifically for qualcomm devices.
Sent from my LG-D802 using Tapatalk
I have a Note 3 N9005.
I installed the latest TWRP recovery.
No matter which rom I try to flash to the system, the same thing happens.
I see that the Aroma installer is strarting and than it just resets for no reason, no install made.
The only sulotion I have found so far is to install a 5.0 stock rom via Odin.
I want to install a custom rom 6.0.1.
Does anyone know what the hell?
Sae problem but a lil worse!!
vashthestampede! said:
I have a Note 3 N9005.
I installed the latest TWRP recovery.
No matter which rom I try to flash to the system, the same thing happens.
I see that the Aroma installer is strarting and than it just resets for no reason, no install made.
The only sulotion I have found so far is to install a 5.0 stock rom via Odin.
I want to install a custom rom 6.0.1.
Does anyone know what the hell?
Click to expand...
Click to collapse
I tried to do the same but ended up bricking my phone. So then I try to unbrick/unroot my phone by flashing the stock rom but I can't do that either cause now it says "Volume Size is too big 4620288<4718599. Need help!!!! ASAP!
Hey guys, I had the same problem at first and it freaked me out too.
Try installing the older 2.8.7.0 version for TWRP through the app, instead of the latest or any other after v3 for that matter. Apparently I've read from other forums that it's due to lack of Aroma Installer Support.
Hope this helps
Confirm the phone's model # by booting into download mode befor flashing TWRP or a stock ROM from sammobile.com.
Will try
I flashed the stock rom packege with odin.
saved my phone after brick.
so you are saying that by downgrading the TWRP recovery i can use aroma insatller based roms again?
cause i also tried to install reserection remix rom (I think this has no aroma in it), i got a massage that said that i cannot install it as well.
refuses to let me change into anything but stock rom.
rooting did not help at all.
vashthestampede! said:
so you are saying that by downgrading the TWRP recovery i can use aroma insatller based roms again?
cause i also tried to install reserection remix rom (I think this has no aroma in it), i got a massage that said that i cannot install it as well.
refuses to let me change into anything but stock rom.
rooting did not help at all.
Click to expand...
Click to collapse
To be honest I don't really know about Cyanogen Mod, however this was just my personal experience with Aroma Installer. I've tried DarkWolf_FW and Aryamod ROMs which are both S7 Edge Port ROMs, and they both use Aroma Installer.
- Also! Take the opportunity to make a Nandroid backup just in case the installation goes bad, then you can restore to where you are right now. Honestly downgrading just worked for me so please don't make me liable if anything goes to pot, at least you will have a full device backup to the exact point in your system which I have found extremely useful when trying different ROMs and Kernels.
tnks
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
vashthestampede! said:
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
Click to expand...
Click to collapse
Hey, just randomly thinking, did you reset all your System, Data and Cache and Dalvik Cache files before you tried to install the ROMs? Sorry, this might not make a difference, but I don't think I have any more advice to give (I'm kinda new to this too ).
Hope CWM recovery goes well, let me know how it goes
vashthestampede! said:
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
Click to expand...
Click to collapse
Doing a complete backup before anything is always the safest bet.
From my experience, TWRP 3+ is fine for CM and AOSP based ROMs.
TWRP 2.8.7-0 is the one you should use to flash ROMs using AROMA Installer.
If you read the OP (opening post) on any ROM forum, it will usually include installation instructions and generally states which TWRP version should be used.
Good Luck.
theawesomecw said:
To be honest I don't really know about Cyanogen Mod, however this was just my personal experience with Aroma Installer. I've tried DarkWolf_FW and Aryamod ROMs which are both S7 Edge Port ROMs, and they both use Aroma Installer.
- Also! Take the opportunity to make a Nandroid backup just in case the installation goes bad, then you can restore to where you are right now. Honestly downgrading just worked for me so please don't make me liable if anything goes to pot, at least you will have a full device backup to the exact point in your system which I have found extremely useful when trying different ROMs and Kernels.
Click to expand...
Click to collapse
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
You just need download mode to flash it.
Sent from my SM-G925F
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
I presume when you say it doesn't turn on you mean it doesn't boot into the Android environment. Have you tried unplugging the battery and pressing the Volume Up + Home + Power Button? Yes... I was surprised you don't have to be an octopus too..
Then restore the Nandroid backup from before.
You can also flash TWRP through Odin without root, have a look at the TWRP website for more info.
re
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
all you need is to flush new stock rom via Odin.
Search the web (like I did) to find a stock rom with 4 .tar files in it.
There should be instructions on how to install but usually all needs to be done is this:
1. load odin 3.*
2. enter the phone in download mode.
3. After you see the line 'add' in odin, load the .tar files to the correct place each (not hard they are tagged by same name)
4. Flush and pray.
5. After a successful install the phone will reboot, this will take a while so don't get streesed.
after about 10-15 min the phone will load again.
Root one more time via odin and try to install again.
vashthestampede! said:
all you need is to flush new stock rom via Odin.
Search the web (like I did) to find a stock rom with 4 .tar files in it.
Click to expand...
Click to collapse
Try Sammobile as they have a large database of firmwares for your phone and the country variants.