Mods, feel free to move it it's the wrong spot!
*second update* Someone suggested using Odin to flash the files in download mode. No connections appear in Odin v3, and in Odin v1.85 nothing happens past "setupconnection". I have all of the stock .img files combined into a .tar file, placed in the PDA section. Nothing happens, it just sits like this http://i.imgur.com/oqx5T.jpg until the battery on the phone dies.
*update* Figured out the version issue was because I didn't have the host file set up properly. I did that, but whenever the updater switches from "download" to "update", it changes my phone to Recovery mode. It won't boot into recovery, just Download mode. Everything else gives the secure boot error.
Running the Bell LG Optimus LTE p930, had it on CM10 nightlies until Saturday night, when it randomly died in an update. Follow this unbricking guide: http://forum.xda-developers.com/showthread.php?t=1597488&highlight=bell Trying to do a CWM restore failed; advanced restore worked on the Boot but not on the System of the rom I had backed up.
When it booted, it came up in English, as Version 20e, apparently unrootable with SuperOneClick (I used 2.3.1, 2.3.2, and 2.3.3), so I used this guide to root it: http://www.androidauthority.com/optimus-4g-lte-p930-bell-root-android-4-0-4-update-v20e-109991/
The bootloader is still locked - trying to reboot in recovery gives this:
-----------
Secure boot error!
Cause: boot certification verify
----------
----------
Enter the fastboot...
Enter the fastboot...
Long time no see!
------------
Attempted to push the original ATT images to the phone (through the original XDA guide), everything went great until I pushed the system.img file. Screen went blank, wouldn't light up/unlock, and now any reboots give me the fastboot error.
I can't repeat any of the unbricking guides, because the LG Software tells me "Version is current, so no need to update!"
I can still get the phone into Download mode, but that's about it. Trying to boot into recovery/do a factory reset gives me the dialogue ("press power to confirm"), but then I get the fastboot issue again.
Am I boned?
liqdnitro said:
Mods, feel free to move it it's the wrong spot!
*second update* Someone suggested using Odin to flash the files in download mode. No connections appear in Odin v3, and in Odin v1.85 nothing happens past "setupconnection". I have all of the stock .img files combined into a .tar file, placed in the PDA section. Nothing happens, it just sits like this http://i.imgur.com/oqx5T.jpg until the battery on the phone dies.
*update* Figured out the version issue was because I didn't have the host file set up properly. I did that, but whenever the updater switches from "download" to "update", it changes my phone to Recovery mode. It won't boot into recovery, just Download mode. Everything else gives the secure boot error.
Running the Bell LG Optimus LTE p930, had it on CM10 nightlies until Saturday night, when it randomly died in an update. Follow this unbricking guide: http://forum.xda-developers.com/showthread.php?t=1597488&highlight=bell Trying to do a CWM restore failed; advanced restore worked on the Boot but not on the System of the rom I had backed up.
When it booted, it came up in English, as Version 20e, apparently unrootable with SuperOneClick (I used 2.3.1, 2.3.2, and 2.3.3), so I used this guide to root it: http://www.androidauthority.com/optimus-4g-lte-p930-bell-root-android-4-0-4-update-v20e-109991/
The bootloader is still locked - trying to reboot in recovery gives this:
-----------
Secure boot error!
Cause: boot certification verify
----------
----------
Enter the fastboot...
Enter the fastboot...
Long time no see!
------------
Attempted to push the original ATT images to the phone (through the original XDA guide), everything went great until I pushed the system.img file. Screen went blank, wouldn't light up/unlock, and now any reboots give me the fastboot error.
I can't repeat any of the unbricking guides, because the LG Software tells me "Version is current, so no need to update!"
I can still get the phone into Download mode, but that's about it. Trying to boot into recovery/do a factory reset gives me the dialogue ("press power to confirm"), but then I get the fastboot issue again.
Am I boned?
Click to expand...
Click to collapse
Exact same here
Secure boot error!
Im Still Working On It If I get A Fix Ill Post
ANyone else:crying:
Batesinc said:
Exact same here
Secure boot error!
Im Still Working On It If I get A Fix Ill Post
ANyone else:crying:
Click to expand...
Click to collapse
I Did A Lg Update Tool Fix Brought It Back To Life
Related
I was an idiot. I should've read the instructions and the new software released, but after successfully flashing my phone a few times, I got cocky. I was running greyblur but wanted to update it to the latest official gingerbread FW. I flashed it using CW, but now it's stuck on the load Motorola screen. It'll turn on, show the motorola icon, show GREYBLUR, then just get stuck in an infinite cycle.
I tried leaving it on for a while, about half an hour and nothing worked.
Tried to fastboot, and give it a hard reset but that didn't lead to anything.
Anyways, I've downloaded the FW 4.1.83, tried renaming it to update.zip and running that but it doesn't work..
Can anyone help me out?
IronicUniqueUsername said:
I was an idiot. I should've read the instructions and the new software released, but after successfully flashing my phone a few times, I got cocky. I was running greyblur but wanted to update it to the latest official gingerbread FW. I flashed it using CW, but now it's stuck on the load Motorola screen. It'll turn on, show the motorola icon, show GREYBLUR, then just get stuck in an infinite cycle.
I tried leaving it on for a while, about half an hour and nothing worked.
Tried to fastboot, and give it a hard reset but that didn't lead to anything.
Anyways, I've downloaded the FW 4.1.83, tried renaming it to update.zip and running that but it doesn't work..
Can anyone help me out?
Click to expand...
Click to collapse
Flash a stock 2.3.4 via moto-fastboot
http://bandbinnovations.com/xda/ging...ead-4.5.91.zip
extract boot.img, system.img from the archive and flash via moto-fastboot.
Download moto-fastboot for your OS here:
http://forum.xda-developers.com/showthread.php?t=1138092
Then do the following commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
This one should boot up without problems
You can upload files to flash i get error in the link to download the 2.3.4 stock
Tavo_an said:
You can upload files to flash i get error in the link to download the 2.3.4 stock
Click to expand...
Click to collapse
http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Yoyomah20 said:
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Click to expand...
Click to collapse
man the same thing happende to me, the only way i could partially recover my phone was flashing clockwork mod and from there install Cianogenmod 9, then in recovery mode conected to the pc via cable and typed:
"adb reboot bootloader"
once in Fastboot mode typed:
"fastboot boot boot.img"
where boot.img is the file contained in the cyanogenmod .zip file, doing this i managed to boot the rom and use my phone, the problem is that anytime it restarts it gets stuck in the boot loop again, and i have to repeat the process for it to boot again, i think is a bootloader problem since i have virtually done anything else, i think that the OTA update from tmobile changes something on the bootloader and it forces recovery/update boot always, and since the OTA never was completed it never got back to it's original state, its´s just my theory, i´m looking into it, but for now my phone works!.
Solution
I found a solution for the lg c800 bootloop, se my post: http://forum.xda-developers.com/showpost.php?p=39453347&postcount=10
Okay, so I rooted my wife's LG C800 (T-Mobile MyTouch Q), with the hopes of finding a decent custom ROM. No luck, went back to stock. Didn't unroot. OTA comes out today. Wife doesn't know any better, and tries the OTA update. Now can't get out of recovery. I've cleared Dalvic (although get an error message "E:unknown volume for path [/sd-ext]", it still says wipe successful), format system, format cache, factory resent and re=flash the stock ROM several times. Still will only boot to ClockworkMOD. I have tried manually flashing the boot.img. Same thing. I tried manually flashing system.img, but it says it's too big. Any ideas would be GREATLY appreciated.
Thanks,
Wulf
Stock Recovery
greowulf said:
Okay, so I rooted my wife's LG C800 (T-Mobile MyTouch Q), with the hopes of finding a decent custom ROM. No luck, went back to stock. Didn't unroot. OTA comes out today. Wife doesn't know any better, and tries the OTA update. Now can't get out of recovery. I've cleared Dalvic (although get an error message "E:unknown volume for path [/sd-ext]", it still says wipe successful), format system, format cache, factory resent and re=flash the stock ROM several times. Still will only boot to ClockworkMOD. I have tried manually flashing the boot.img. Same thing. I tried manually flashing system.img, but it says it's too big. Any ideas would be GREATLY appreciated.
Thanks,
Wulf
Click to expand...
Click to collapse
On a side note, any ideas how to go back to stock recovery on the LG C800?
Thanks in advance!
I have the exact same problem
Any help would be appreciated.
Thanks
Any luck yet Greowulf?
ng1and said:
Any luck yet Greowulf?
Click to expand...
Click to collapse
Nope, ended up having to replace it. Unlike my HTC Doubleshot, this LG C800 just doesn't have a robust dev community. I think I'll keep her on the stock recovery and ROM until we can afford a better phone. . .
Bummer
Guess I'll have to do the same thing. I'm going to try taking it to a store but I doubt they'll help since it's jailbroken. I'll update when I do.
Thanks for letting me know.
I have the same problem
Hi, i have the same problem, but when i flashed the original recovery that i downloaded from de clockwork mod recovery post my phone died, now when i turn it on it does the same thing (it always boot to recovery) as before but with the original recovery, when it tries to boot the original recovery it doessen´t do anything and restarts which starts the same process again (boot in recovey for 1 second and restarts), any idea to get my phone back???
Update on my problem
Hello i´ve manage to put my phone in S/W Upgrade mode but i try to use the LGMobile Support Tool to restore my phone to its original state, in this process it stops about twelve seconds in and tells me that an error ocurred and it cant continue with the process, i´ve tried fastboot keys to but in that mode but it boots directly into recovery mode and stays in a loop of reseting and going in to recovery mode (in this mode i can't do anything on my pc because it appears and disapears to fast), the only way i´ve managed to use pc tools is by putting it in S/W Upgrade, in my pc i can see a serial port, a modem and a Lg android phone, but in cmd using "adb device" nothing appears, any idea on what to do next?
mr arrieta said:
Hi, i have the same problem, but when i flashed the original recovery that i downloaded from de clockwork mod recovery post my phone died, now when i turn it on it does the same thing (it always boot to recovery) as before but with the original recovery, when it tries to boot the original recovery it doessen´t do anything and restarts which starts the same process again (boot in recovey for 1 second and restarts), any idea to get my phone back???
Click to expand...
Click to collapse
Ok, if you have this problem plss never restore to the original recovery before solving it, if you flash your original recovery you might end up worst, all you have to do in this case is restoring the backup you made when installing clockwork mod, if you are like me and never did one or erased it later on, i´ve been trying to see how to fix my phone, and the closest i am of making it work is flashing CyanogenMod through CWM then i enter fastboot mode and make it boot from the extracted boot image from the CyanogenMod .zip file, i dont have a permanent fix, but ill keep you posted.
Partial solution
Hello, i foud i very nasty solution but it works for now is the only way i know to fix Lg c800 bootloop, this was only tested with Cyanogen mod 9 latest nightly, to force always your phone to boot os and not the recovery i repaced the phone's recovery.img with the boot.img contained in the cyanogen mod .zip file, here's a step by step guide.
1. Download latest nightly Cyanogen mod 9 for lg c800 release .zip
2. Flash this image with the clockworkmod recovery
3. In recovery mode connect your phone to the pc and with adb and fastboot installed
4. Reboot your phone to fastboot mode typing: "adb reboot bootloader"
5. Once in fastboot (lg logo with black screen) type: "fastboot flash recovery boot.img", for this to work you must have your boot.img extracted from the cyanogen mod9 zip file in the same directory as your adb and fastboot .exe
6. Reboot your phone typing: "fastboot continue"
And when this is finished your phone boots drectly to your installed Cyanogen mod 9 firmware, there are some side effects to this fix, because it is no final, the side effects are:
1. Your phone does not have recovery now, if you boot it in recovery mode or normal mode it always boots to your Cyanogenmod 9 ROM, you can always boot your recovery manually from the pc in fastboot by typing "fastboot boot recovery.img", for this to work you must have your recovery.img extracted from the Clockwork recovery zip file in the same directory as your adb and fastboot .exe
2. This fix only works for custom roms, if you try this with a stock 2.3.6 o 2.3.4 Rom your phone wont boot and you will have to start over, it only worked for me with Cyanogen mod 9.
I hope you can take back to live your phones as i did, if you're stuck in bootloop and dont have clackwork mod installed into your device, you have to flash a custom kdz rom that contains clockwork recovery an then do what´s on the guide, i have a custom kdz to do this but have no place or time to upload it, as soon as i con i will post it.
---------- Post added at 04:59 PM ---------- Previous post was at 04:24 PM ----------
PLSSSS be aware that if you do this wrong (by using a stock rom instead of cyanogen mod 9) and dont have the .kdz that flashes clockwork recovery to your phone, you might end up worst than before, but in my experience i always had adb acces to the phone when using cyanogen mod 9, to restore your phone if something goes wrong and you have adb acces type:
"adb reboot bootloader"
"fastboot erase recovery"
"fastboot flash recovery recovery.img", for this to work you must have your recovery.img extracted from the Clockwork recovery zip file in the same directory as your adb and fastboot .exe
"fastboot continue"
and your are done, now you have cwm recovery installed in your phone and stuck in bootloop again.
Plss if you don't have adb acces flash this kdz image (this is pending, i'm uploading it but i think it will be available on tuesday), is a custom rom that mounts clockwork recovery and other usefull stuff to recover your phone in this method (this kdz wot fix your bootloop problems, only mounts clockworkmod recovery to your phone so you can follow the guide, flash roms and have a adb acces)
ng1and said:
Bummer
Guess I'll have to do the same thing. I'm going to try taking it to a store but I doubt they'll help since it's jailbroken. I'll update when I do.
Thanks for letting me know.
Click to expand...
Click to collapse
Don't take it in, call in. They'll walk you through trouble shooting and mail you a new one if it's still in warranty. LG will do the same if you're not with T-mobile, but you'll have to pay for shipping
Link
this is the link for the kdz image i made: https://www.dropbox.com/s/p4ozl5wwdtwsub0/V10V_00 mia CWM y Cianog.kdz, this one installs clockworkmod to your phone's recovery, flash it to follow the guide i posted before.
Has anyone found a full solution? I am stuck just like the first post, i can get to cwm recovery but it is stuck in a continuos loop back to recovery. I haven't tried mr arrieta still as i need a full solution to this. I have backup in my sdcard of the original recovery i took from flash boot, a copy of the stock rom that is rooted and the lastest Cyanogenmod 9.
I tried using a zip I found called exitrecovery.zip but it didn't work. Should i try to install the original recovery with the stock rom and try to do a factory reset with LG PC Suite software??
I would really appreciate some help here.
I have my father's MyTouch Q that was rooted and is now in a boot loop. It only stays active (as far as being connected by usb) for about 2-3 seconds so I don't have enough time to put it into fast boot or really do anything with it unless I can figure out how to keep it active longer. I have tried many of the possible fixes and yet I am still banging my head against this desk. I would appreciate any help on this matter.
BigDv said:
I would really appreciate some help here.
I have my father's MyTouch Q that was rooted and is now in a boot loop. It only stays active (as far as being connected by usb) for about 2-3 seconds so I don't have enough time to put it into fast boot or really do anything with it unless I can figure out how to keep it active longer. I have tried many of the possible fixes and yet I am still banging my head against this desk. I would appreciate any help on this matter.
Click to expand...
Click to collapse
To keep active longer you need to put you'r phone into S/W update mode by pressing E+volup+pwr, in this mode you can flash via KDZ updater the .kdz file i compiled and published, if you complete correctly this steps your phone should be booting into cwm recovery from there you have to flash the latest cm9 nightly and via fastboot replace your recovery with the boot.img contained in the cm9.img.
when you finish this process you should have a phone that has no recovery mode but always boot into the rom directly, that is how i've been using my phone till i have time to find a solution with recovery mode.
---------- Post added at 12:46 AM ---------- Previous post was at 12:37 AM ----------
Altaflux said:
Has anyone found a full solution? I am stuck just like the first post, i can get to cwm recovery but it is stuck in a continuos loop back to recovery. I haven't tried mr arrieta still as i need a full solution to this. I have backup in my sdcard of the original recovery i took from flash boot, a copy of the stock rom that is rooted and the lastest Cyanogenmod 9.
I tried using a zip I found called exitrecovery.zip but it didn't work. Should i try to install the original recovery with the stock rom and try to do a factory reset with LG PC Suite software??
Click to expand...
Click to collapse
Hello i've tried all solutions you can find on the internet and none seem to work, i restored original backups, tried zip files, etc... the probles is that if you flash the stock recovery you will end up worst because you will have to us the kdz programer to recover the CWM and your phone will be in a bootloop of 3 seconds in which you can do less.
for now there is no full solution, since i think i am the only one working on this and i don't have the time for this project, when i bricked my phone i needed a fast solution and that is what i have and posted.
my solution makes your phone to boot always into the OS partition so your phone will always work, but you will not have a recovery.
Update
Hello, i've learned a lot of stuff since last time, but i have no solution yet, i'm hoping some one will read this and help me get to a solution since i've read a lot and there are still lots of stuff i cant seem to make out (@chui101).
First i tried a couple of solutions i found online for fixing CWM recovery loop after ota, but one of them bricked my phone even worst, i ended up in a qualcom high speed conection with black screen and no GUI, i thought my phone was dead forever (i've felt that way a lot lately but it always seems to find the way to come back to life ), i managed to get my phone back to life with QPST and some files i got out a KDZ file, but i was still in the CWM recovery loop.
I continued my research and found out that it is mostlikely fault of the misc partition that stores data between phone modules, so i got my phone partition table and began looking in the original boot.img and recovery.img files to find any piece of information i could get my hands on, since this phone has very little info out there and tried to find any comand that would reset the ota update flag that began all this, in this process i bricked my phone fastboot mode and had to do a full brick and fix with QPST since KDZ didn't seemed to do the trick, here is what i got so far as partition table goes:
mmcblk0p1 ----->
mmcblk0p2 ----->
mmcblk0p3 ----->
mmcblk0p4 ----->
mmcblk0p5 ----->
mmcblk0p6 ----->
*mmcblk0p7 -----> boot
mmcblk0p8 ----->
mmcblk0p9 ----->
mmcblk0p10 ----->
mmcblk0p11 ----->
mmcblk0p12 ----->
mmcblk0p13 -----> rmt storage
mmcblk0p14 -----> rmt storage
*mmcblk0p15 -----> system
*mmcblk0p16 -----> data
*mmcblk0p17 -----> recovery
*mmcblk0p18 -----> cache
mmcblk0p19 -----> rmt storage
mmcblk0p20 -----> wifi pemission root
mmcblk0p21 -----> DivX cache
mmcblk0p22 ----->
mmcblk0p23 ----->
mmcblk0p24 ----->
*mmcblk1p1 -----> sd card
I cant seem to locate which one is the misc partition yet, my theory is that if i can identify this partition some one that has a working lg c800 Mytouch Q cand back up this partition for me as a misc.img and with it i could restore my phone to a correct working state, since i foud online a nandroid backup but it didn't fixed my loop.
Other Approach
Another option i thought is to mod an original boot.img to boot directly to the kernel img and trigger a new OTA from there with the unrooted phone and original recovery, but i cant seem to make this right, since i unpack the original boot.img and then without changing anything i repack it and only by doing that the newboot.img doesn't do anything it freezes on the LG logo of the fastboot mode.
I'm using boot kitchen.rar i found online which uses split_bootimg.pl to get out kernel and ramdisk from image, then 7Zip to extract ramdisk.gz and its content, then repacks it with mkbootfs.exe and with mkbootimg.exe, the command i'm using for making the boot image is:
"mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-new.gz -o newboot.img --base 0x00200000"
but ive tried with --cmdline option (using the comand line message it gives me when extracting, and my mkbootimg.exe does not recieve the --base comand), and tried in different order but newboot.img doese't work.
Any ideas, any developers, any mod? any something????
LG myTouch Q (C800) Stuck on LG Logo Fix Solution !
:good: :good::laugh:
mobiletek909 said:
:good: :good::laugh:
Click to expand...
Click to collapse
Will this make me lose root or relock the phone?
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Does anyone have a suggestion how I can get Fastboot fixed and the Nabi back to "normal" / upgradeable.
Thanks for your help
kaijan said:
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
Click to expand...
Click to collapse
What software rev did you get to when doing the OTA's?
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
Click to expand...
Click to collapse
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Click to expand...
Click to collapse
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
aicjofs said:
What software rev did you get to when doing the OTA's?
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Verifying current system...
assert failed: apply_patch_check("/system/app/Gallery2.apk", "4cadedee1defcdc28afc99ea968ebb1e631e7b9", "ee310bfc0d0ad2fe11356b97f8cb6e754aa43f2b")
E: Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
kaijan said:
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Click to expand...
Click to collapse
Hmm that is it weird. It does look like gapps is still installed .As gapps removes gallery2.apk and why it's failing, I don't understand if it's stock how that is happening. Use these updates yet? http://forum.xda-developers.com/wiki/Fuhu_nabi_2
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
hotspace said:
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
Click to expand...
Click to collapse
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
I did try ADB REBOOT-BOOTLOADER all that happens is the NABI2 restarts and sits at the logo screen.
I'm able to push via ADB, so I will download the suggested files and take your advice. I'll report back. And, thanks for the reply.
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
hotspace said:
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
Click to expand...
Click to collapse
Nah Nabi2 is practically impossible to brick.
So do you get the command list in the top left when you press the vol and power buttons? i.e the selection continue, fastboot, recovery kernel, forced recovery? or when you select recovery kernel it just doesn't boot TWRP?
I wont type a lot of stuff until I get you answer but if we need to go the nvflash route this is some good reading. You will need to get in to APX mode, install the driver and issue some commands.
Read this post and next few pages after it
http://forum.xda-developers.com/showpost.php?p=46579190&postcount=1687
General idea of commands
http://forum.xda-developers.com/showpost.php?p=48683262&postcount=124
Might be some work, but we should be able to get the device back, I'll let you know which is the best way after I see your reply.
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
aicjofs said:
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
Click to expand...
Click to collapse
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Get the nvflash package from the Nabi General Info thread I linked above
Unzip in to a directory of your choosing and open a command prompt in that folder
The Nabi will be broken open and connected by USB to computer
So once you get those pins shorted and press the power button the screen should come on and be completely black(you can tell the backlight is on though)
Check in device manager for a new device(it will be auto detected or you will have to manually install APX driver)
Once the driver is installed you can issue nvflash commands
nvflash --bl bootloader.bin --download 4 bootloader.bin
Before pressing enter for the below command get ready to press and hold the vol+ key.
nvflash --resume --go
Right on. I'll dig into this in the morning
Sent from my SM-N920P using Tapatalk
@aicjofs, I still haven't begun breaking the Nabi down. I'm working from home today and should be able to squeeze the disassemble in sometime today.
I scanned through the comments you've left since finding out I wasn't able to get to the boot menu...I'll post back once I get it torn apart.
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
BigZ1 said:
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
Click to expand...
Click to collapse
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
BigZ1 said:
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
Click to expand...
Click to collapse
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.