Yesterday I tried to upgrade to Kitkat but it didn´t work out so well. Now I´m stuck in bootloop. Device doesn´t get beyond the LG-logo. Unfortunately I also can´t boot into download mode any more - but I can get into CWM-recovery.
The question is, how to unbrick from there.
I already tried to flash another ROM (Aonflex). The installation process finished succesfully, but after reboot I´m still in bootloop.
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Another thing is that every time I want to exit from CWM, it asks: "Root access is missing. Root device No/Yes". I used to be rooted but now that seems to have changed. Could this be part of the problem?
I also tried flashing the original F320L firmware (.kdz-file) with "R&D Test Tool", but also without success.
I´m on the Korean variant F320L and would really need some help. Any suggestions?
Parinibbana said:
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Click to expand...
Click to collapse
I think you forgot to copy the MegaLock.dll to the LGFlashTool folder (over the existing one).
Phoost said:
I think you forgot to copy the MegaLock.dll to the LGFlashTool folder (over the existing one).
Click to expand...
Click to collapse
Thanks for the hint, but in fact I did not forget about it. I did replace the original one.
Parinibbana said:
Yesterday I tried to upgrade to Kitkat but it didn´t work out so well. Now I´m stuck in bootloop. Device doesn´t get beyond the LG-logo. Unfortunately I also can´t boot into download mode any more - but I can get into CWM-recovery.
The question is, how to unbrick from there.
I already tried to flash another ROM (Aonflex). The installation process finished succesfully, but after reboot I´m still in bootloop.
Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
Another thing is that every time I want to exit from CWM, it asks: "Root access is missing. Root device No/Yes". I used to be rooted but now that seems to have changed. Could this be part of the problem?
I also tried flashing the original F320L firmware (.kdz-file) with "R&D Test Tool", but also without success.
I´m on the Korean variant F320L and would really need some help. Any suggestions?
Click to expand...
Click to collapse
Give this a try. It sounds like it will help.
http://forum.xda-developers.com/showthread.php?t=2582142
Thanks Toopty, for the interesting thread. Unfortunately there is no TWRP for the Korean F320L so far. Secondly, my phone keeps booting and shutting down, so it is not possible to push files to the phone during this process. Of course it is also not recogniced by the device manager of the computer during bootloop. Only from within CWM-recovery can the phone be detected by the computer. But even if we were to find TWRP for my F320L, I am not sure whether this could/should be installed in addition to CWM.
I assume one would not need to install TWRP at all if CWM is installed already. Therefore pushing the first 4 out of 5 files should be sufficient.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
What do you think?
But since CWM says that "Root access is missing", I am not sure whether this method would work at all. Is there a way to regain root from within CWM? Do I even need root-access in the present state, or would it be enough to root again after the bootloop-problem is solved.
Stuck in bootloop but can push files using adb-commands
I would like to add, that I can push files to the device over adb when I am inside CWM-recovery. I can even flash ROMs, but all that doesn´t help, since afterwards I will still be in bootloop.
If I knew which files are corrupted causing the device not to get beyond the LG-bootlogo, then I could replace the corrupted files over adb.
Any ideas?
Parinibbana said:
Thanks Toopty, for the interesting thread. Unfortunately there is no TWRP for the Korean F320L so far. Secondly, my phone keeps booting and shutting down, so it is not possible to push files to the phone during this process. Of course it is also not recogniced by the device manager of the computer during bootloop. Only from within CWM-recovery can the phone be detected by the computer. But even if we were to find TWRP for my F320L, I am not sure whether this could/should be installed in addition to CWM.
I assume one would not need to install TWRP at all if CWM is installed already. Therefore pushing the first 4 out of 5 files should be sufficient.
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
What do you think?
But since CWM says that "Root access is missing", I am not sure whether this method would work at all. Is there a way to regain root from within CWM? Do I even need root-access in the present state, or would it be enough to root again after the bootloop-problem is solved.
Click to expand...
Click to collapse
I would try to use the method i suggested to restore your Download mode, I can confirm that it will work. Then use download mode to flash the factory *.kdz or *.tot file to your device via the LG recovery tool. I'm not an expert at this, but i think you should focus on getting download mode working, then you can restore your phone to stock fixing whatever partition is broken and keeping your phone from booting. This will get your phone back to a factory stock and booting condition, then work on modding it to the way you want.
As a side note If TWRP is not available for your device i would assume you could just substitute CWM in its place. This really doesn't matter if your only trying to get to download mode to restore your phone.
Have you tried ADB Sideload?
MK45A said:
Have you tried ADB Sideload?
Click to expand...
Click to collapse
No, what is it? How would ADB sideload help in my situation?
Do I even need it, since I can flash any ROM successfully from within normal CWM-mode and have full access to adb-commands from within CWM. But whatever ROM I flash, afterwards I am still stuck in bootloop.
How could sideload help with that?
Parinibbana said:
No, what is it? How does ADB sideload work?
Click to expand...
Click to collapse
In CWM, look for something like 'ADB Sideload' and then enable it.
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
Parinibbana said:
No, what is it? How does ADB sideload work?
Click to expand...
Click to collapse
ADB sideload lets you push roms from your pc using command prompts to your phone.
---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------
Have you tried out LG FlashTool?
MK45A said:
Have you tried out LG FlashTool?
Click to expand...
Click to collapse
Yes, as mentioned above: ...Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
What does "CrossDL [ ] to [F320L]..." mean?
Parinibbana said:
Yes, as mentioned above: ...Then I tried to get back to stock using a method described at optimusforums.com which is called "complete guide to unbrick your soft bricked g2" and which worked a few months ago when I also had a bootloop. I am using the exactly same files and method as then, but now I get an error in LG FlashTool saying smthg. like "CrossDL [ ] to [F320L]...".
What does "CrossDL [ ] to [F320L]..." mean?
Click to expand...
Click to collapse
Can you write down the whole error or provide screenshots?
MK45A said:
ADB sideload lets you push roms from your pc using command prompts to your phone.
Click to expand...
Click to collapse
I see. This means, I don´t need to push the zip file to /sdcard/ beforehand, but can flash it directly from the laptop, right?
Here is a screenshot.
Concerning the method outlined in: http://forum.xda-developers.com/showthread.php?t=2582142
Already tried it out the day before yesterday but didn´t get very far because of this reason:
After command: "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
But shouldn´t the list be much longer such as: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
I concluded, however, that sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
That´s it. Already posted on page 32 and 33 of that thread, but so far I didn´t get any answer as how to overcome this error. Does it mean that the phone isn´t mounted or what? I´m not familiar with Ubuntu.
Do you have a clue how to proceed from here?
Parinibbana said:
Concerning the method outlined in: http://forum.xda-developers.com/showthread.php?t=2582142
Already tried it out the day before yesterday but didn´t get very far because of this reason:
After command: "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
But shouldn´t the list be much longer such as: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
/dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
/dev/sdb5 .......... /dev/sdb36
I concluded, however, that sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
That´s it. Already posted on page 32 and 33 of that thread, but so far I didn´t get any answer as how to overcome this error. Does it mean that the phone isn´t mounted or what? I´m not familiar with Ubuntu.
Do you have a clue how to proceed from here?
Click to expand...
Click to collapse
Today I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted.
Finally unbricked my phone.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of this thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
Parinibbana said:
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of this thread: http://forum.xda-developers.com/show....php?t=2451696
Click to expand...
Click to collapse
Interesting. Thanks for the feedback.
Download minimalabd https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Run this in adb
copy and past
adb shell
and also
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
and also past on cmd
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
This fixed my phone
NP
Related
my lg optimus l5 E612 keeps rebooting itself after the media scan. this didn't happen untill i unlocked the bootloader and installed CWM. i have tried to wipe the cache, the dalvik cache and a factory reset in CWM but still kept rebooting. So I restored the original bootloader and recovery than done a factory reset and that stopped it. I downloaded the the ulocked bootloader from a diffident website and tried doing it again but still did it. how can i fix it??
The solution !!!!!!!!!!
Enable USB debug (before your phone reboots).......... very fast!
first
you must have patched you phone with recovery (mmcblk0p17) and boot (mmcblk0p5) partition
This file is extracted from the russian firmware....... is the bootloader!!!
I try this process with my phone (lg e612f)...... and no more reboots
copy the file to the sdcard
docs.google.com/file/d/0B-im6Vo1WjAEV1phbWRLOXIzX00/edit?usp=sharing
run from ADB
adb shell
su
dd if=/sdcard/immcblk0p9 of=/dev/block/mmcblk0p9
reboot recovery
enjoy...... your phone is unlocked!!!!!!!
willthis work with mine because mine is not the f model
didn't work still reboots
Jayd3n_420 said:
didn't work still reboots
Click to expand...
Click to collapse
did u get it working???
continous rebooting problem on lg l5 e612 f got resolved
thanx xda developers...!!!!!
---------- Post added at 11:36 AM ---------- Previous post was at 11:31 AM ----------
JReynaldo 117 said:
Enable USB debug (before your phone reboots).......... very fast!
first
you must have patched you phone with recovery (mmcblk0p17) and boot (mmcblk0p5) partition
This file is extracted from the russian firmware....... is the bootloader!!!
I try this process with my phone (lg e612f)...... and no more reboots
copy the file to the sdcard
docs.google.com/file/d/0B-im6Vo1WjAEV1phbWRLOXIzX00/edit?usp=sharing
run from ADB
adb shell
su
dd if=/sdcard/immcblk0p9 of=/dev/block/mmcblk0p9
reboot recovery
enjoy...... your phone is unlocked!!!!!!!
Click to expand...
Click to collapse
thnx.....this really helped a lot
the link is broken man! fix it for me plz.
JReynaldo 117 said:
Enable USB debug (before your phone reboots).......... very fast!
first
you must have patched you phone with recovery (mmcblk0p17) and boot (mmcblk0p5) partition
This file is extracted from the russian firmware....... is the bootloader!!!
I try this process with my phone (lg e612f)...... and no more reboots
copy the file to the sdcard
docs.google.com/file/d/0B-im6Vo1WjAEV1phbWRLOXIzX00/edit?usp=sharing
run from ADB
adb shell
su
dd if=/sdcard/immcblk0p9 of=/dev/block/mmcblk0p9
reboot recovery
enjoy...... your phone is unlocked!!!!!!!
Click to expand...
Click to collapse
the link is broken! plz fix it.
My L7 is rebooting
Hello to all,
My Lg Optimus L7 sudenly restarts when using it little longer. When i'm start to play some game like Temple run it cannot last for a few minutes, apps start to crush like android proces has stoped, google play has stoped etc... and than sudenly restarts itself... then i have to remove baterry and live the phone to "cool" for a while, and than i can turn it on when everything works normaly util next longer using... this is happening even when using other apps like skype for a little longer...I have tried to flash new software, even to instal prerooted software and do a factory reset through CMW, dalvik, cache, fix permisions but nothing helped, always the same... HELP!
I would try this method above but the LINK IS BROKEN...
Thanks in advance
Hello,
I have exactly the same problem with my Optimus L5 after unlocking the bootloader. Any idea where this problem comes from and how to solve it?
Did you use the exact bootloader for your model?
See this post
Thanks for the answer,
I used this OL5_1.0
http://forum.xda-developers.com/showthread.php?p=38053729
Also according to Android my phone is E610, but on the back it's written E610/E612F, so which one should I try?
Last problem, since I have installed Cyanogenmod there is no more "charge only", I don't know if it's really important though. I will try to have yours work.
Mautho said:
Also according to Android my phone is E610, but on the back it's written E610/E612F, so which one should I try?
Last problem, since I have installed Cyanogenmod there is no more "charge only", I don't know if it's really important though. I will try to have yours work.
Click to expand...
Click to collapse
In android the model can be changed by modifiying one line of build.prop, so i'll trust what the back of the phone says...
To me, while connecting usb is the same on pc... nevermind the "charge only"
I was about to commit suicide because I couldn't get adb working. But finally I managed to enter those 3 commands in the integrated Terminal Emulator, having previously installed the file for E610:
Code:
su
dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5
reboot
And it worked. That was quite hard because I only had 2 minutes between the boot and the reboot. Thanks for helping me. :good:
LG e612f keeps rebooting!!
Hello Guys Ive had trouble with my LG L5 e612f, I unlocked the phone and it keeps on rebooting after 2 minutes... This forum is the only one that has posted a solution to my problem but I am a noob...I really dont understand what to do and where to get the download files for this process since the download links are broken...can someone be kind enough to guide me or probably make a youtube video..please guys. I AM WILLING TO PAY ANYONE THAT CAN HELP!!!!!!!!!!!!!!
hey mate where did you get the download...the download link provided is dead.
Real fix for the lg l5 e612f rebooting and rebooting
Jayd3n_420 said:
didn't work still reboots
Click to expand...
Click to collapse
hey guys I had the same problem and I fixed it i downloaded this bootloader and it worked..
chrome://mega/content/secure.html#!C5JB0D5R!dNifZynT89rsp8bj8dh5Hnc-I44JqtircUQiicUpa7U
the commands I typed were
adb shell
su
dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5
dd if=/sdcard/external_sd/emmc_appsboot.bin of=/dev/block/mmcblk0p5
IT WILL DEFINATELY WORK GUYS.. ENJOY!!
(if the download link asks for decryption key jst delete the last dots and ti(....it) from the url above.
the link provided is no longer exist i have same problem with my lg e610/e612f
JReynaldo 117 said:
Enable USB debug (before your phone reboots).......... very fast!
first
you must have patched you phone with recovery (mmcblk0p17) and boot (mmcblk0p5) partition
This file is extracted from the russian firmware....... is the bootloader!!!
I try this process with my phone (lg e612f)...... and no more reboots
copy the file to the sdcard
docs.google.com/file/d/0B-im6Vo1WjAEV1phbWRLOXIzX00/edit?usp=sharing
run from ADB
adb shell
su
dd if=/sdcard/immcblk0p9 of=/dev/block/mmcblk0p9
reboot recovery
enjoy...... your phone is unlocked!!!!!!!
Click to expand...
Click to collapse
(the link is not working please anyone can give me this the file my lg e612 is keeping on automatically reboot)
Hi all,
First off I've tried now for a two days to solve this, reading as much as I could find on here and the rest of the internet.
I decided to root my LG D802 running 4.2 and install CWM recovery no problem. Next I flashed a stock 4.4.2 vodaphone img. All went well untill i tried to use the touch screen, which shows that when i press on one point on the screen it selects multiple points basically its unusable and unable to do almost anything with it, however i have managed to turn on ADB and connect to the phone. So now i have a stock recovery and an unusable ROM.
So next up I tried to rooting it since I had ADB shell working ok, using the IOROOT25. This appears to work as when it reboots and installs the kkroot.zip in the recovery it's saying it worked. Now when I reboot and open ADB shell then type SU to get root I can't press ok when superuser pops up to asking me to give it permission, because of the touch screen problem.
If i can get root in ADB then remount the files system then i will be able to DD a new recovery img??
After getting this far and loosing, I then found this: http://forum.xda-developers.com/showthread.php?t=2432476 on flashing to stock, but the program crashes every time it's about to flash, so i tried doing a fresh install of windows 7 and then tried windows 8 however the program still crashes every time and yes I have followed the instructions and tried the manual method and checking the 127.0.0.0. lgblahblah is there
So no I am turning to you guys for help.
phone details;
Model: D802 32GB
Firmware operator: VDF
sw version: D80220a
ro.build.fingerprint: lge/g2_vdf_com/g2:4.4.2/KOT49I.D80220a/D80220a.1392133741:user/release-keys
Recovery: <3e> KOT49I.D80220a test-keys
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
need help
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
twon23 said:
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
Click to expand...
Click to collapse
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Ok so your phone not longer boots, correct? Do you know what build/version plus any other details of the rom you flashed? or even a link so i can have a look at the rom you have installed. Can you get into recovery mode and is it still a stock recovery image? also what is your phone d802? 16gb 32gb?
Mustafa1 said:
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Click to expand...
Click to collapse
If you're running root.bat as an admin, try executing it without admin privileges. Dunno why, but it seemed to work for me.
Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
makgun said:
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
Click to expand...
Click to collapse
NOT CWM , it is TWRP
Are you from turkey?
twon23 said:
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
Click to expand...
Click to collapse
Hi! I've recently flashed an updated stock ROM and have the same Touchscreen issue as yourself! Can you tell me the steps you have done to fix it? I'm using windows 8.1 to flash etc, and using a stock ROM I can't seem to get it to work again
Hello there users. I'm currently a dev for Nokia X but I would love to help you guys out.
So, I'll be giving out ways on how you can try to get Root on your device. This is a discussion thread.
As I don't have the device myself, I'm counting on people who have purchased it.
So lets start. In order to get development for your device, you need to get a system dump of your whole/entire device.
But for that, you need Root. Heres an app that I think might root the device. http://www.cydiaimpactor.com/
Goto the link, download it and test it out. Give feedback.
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
stutofa aregercisr are
Thanks for your help, I tried it out and got this error all the time
Altivex said:
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
Click to expand...
Click to collapse
tdiddy.2 said:
Thanks for your help, I tried it out and got this error all the time
Click to expand...
Click to collapse
Okay, so that didnt work.
Now, goto this link and download the adb and fastboot drivers for Nokia X and install them.
After that, go HERE and flash CWM Recovery for Nokia X using the instructions given in the thread.
DONT DO THE ABOVE METHOD! As there is no backup, if something goes wrong, you'll lose the device. For now, wait and let me find more exploits. Till then, do install the adb and fastboot divers.
After that, goto ADB folder and Open command prompt from there (Shift + Right mouse button). Then type this:
Code:
adb reboot bootloader
fastboot -i 0x0421 devices
And see if the device gets recognized.
Then type:
Code:
fastboot -i 0x0421 reboot
You can try this method too: http://forum.xda-developers.com/showthread.php?t=803682
Okay will try. For the recovery, I tried both Nokia X's CWM and TWRP already, none of them worked However it's not going to brick my device haha
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Altivex said:
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Click to expand...
Click to collapse
adb_usb.ini is important as it is the key that recognizes the adb device to the computer.
Do all the above steps in the guide fully including the adb_usb.ini step.
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
http://forum.xda-developers.com/showthread.php?t=2783157
or in attach.
Copy all data to phone, then go to folder "1" install tr.apk
Make shure you`ve got internet connection.
in folder "2" is SUpersu apk.
In folder"3" - root explorer.
Also you`ll find apk for backup phone.
Altivex said:
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Click to expand...
Click to collapse
Thats it. You got the fastboot recognized. Now try Bin4ry Root Method and see if it'll work.
tdiddy.2 said:
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
Click to expand...
Click to collapse
You also got fastboot recognized. f901c863 is your fastboot device number.
Try Bin4ry root method.
Altivex said:
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
Click to expand...
Click to collapse
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Dom3616 said:
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Click to expand...
Click to collapse
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Altivex said:
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Click to expand...
Click to collapse
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Dom3616 said:
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Yes yes!!
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
Yes, you can use this also: http://forum.xda-developers.com/showthread.php?t=1620255
After creating the backup, upload it to Google Drive or any other server.
Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
I tried to pull and got the recovery img for ya hope this work
Native recovery or custom?)
native I`ve restored yesterday from navifirm. And custom will make our life a bit easyer)
I`ve made a twrp backup, with nandroid . Backup have files with .win extension....
Hi.
Bit of a fail of a day for me, as i seem to have bricked my D802 G2.
It started after flashing the latest dorimanx kernel over CloudyG2 3.3.. Afterwards i was stuck in fastboot mode.
After lots of messing around, i used the TOT method to recover and get back to stock..
Then i used srktools to root, and autorec to get TWRP installed. However after the reboot i was stuck with a black screen bootloop, stupidly i then sideloaded and flashed cloudy over the top..
I can still get into TWRP and Download mode, however TWRP cannot mount any of the partitions - so I attempted to re-flash stock using both TOT and KDZ method however nither work (TOT method just skips the partitions for some reason)
UPDATE: Managed to get it fixed - after trying many things including the 9006 QHUSB fix in SRKtools this adb patch finally allowed me to reflash a stock rom:
http://forum.xda-developers.com/lg-g2/development-d802/fix-lg-flash-tool-stuck-2-t3031112
hi, you could try to get in QHSUSB MODE and then flash partitions using linux's dd command
I do NOT recommend this idea, there could a better solution
you should backup all your current partitions (or important ones), dd will do the trick
force enter to QHSUSB: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
how to flash partitions: http://forum.xda-developers.com/showthread.php?t=2582142
link for 10b 16GB d802 partitions: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
lenesul said:
hi, you could try to get in QHSUSB MODE and then flash partitions using linux's dd command
I do NOT recommend this idea, there could a better solution
you should backup all your current partitions (or important ones), dd will do the trick
force enter to QHSUSB: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
how to flash partitions: http://forum.xda-developers.com/showthread.php?t=2582142
link for 10b 16GB d802 partitions: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
Click to expand...
Click to collapse
Thanks - I think the phone has been in QHUSB mode a couple of times - there have been some occasions where many drive letters have appeared in windows when the phone reboots attached to USB.. I will see if i can get it to happen again then connect to a linux machine.
Ive also just noticed that when the phone is stuck on the LG bootscreen and connected to USB, its showing up as a ADB device and i can run ADB commands through it.
NeoVR said:
Ive also just noticed that when the phone is stuck on the LG bootscreen and connected to USB, its showing up as a ADB device and i can run ADB commands through it.
Click to expand...
Click to collapse
i don't know if ADB could help you if TWRP can't mount partitions
I remember there was a command to boot to a *.img sent from PC, but I don,t know if it was fastboot or adb (pretty sure it was fastboot)...
what's your twrp version?
have you tried the new LGUP?
lenesul said:
i don't know if ADB could help you if TWRP can't mount partitions
I remember there was a command to boot to a *.img sent from PC, but I don,t know if it was fastboot or adb (pretty sure it was fastboot)...
what's your twrp version?
have you tried the new LGUP?
Click to expand...
Click to collapse
Its fastboot that can send img files (im trying to avoid that as it would mean destroying download mode)
twrp is 2.7.0.0
Ive also tried LGUP, it detects the phone but cant detect the version - i cant find where to edit build.prop to force it to recognise.
Update: ITS FIXED!
In the end it was this that fixed it: http://forum.xda-developers.com/lg-g2/development-d802/fix-lg-flash-tool-stuck-2-t3031112
as i had adb access i thought id give it a go, and the TOT flashed correctly after.
Many thanks everyone!
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Your first link for the userdata image says file not found when you go to that link.
UPDATED USERDATA
freedomwarrior said:
Your first link for the userdata image says file not found when you go to that link.
Click to expand...
Click to collapse
Sim unlock
Hey guys,
has anyone managed to find a way to simunlock this phone? I bought one on blackfriday for $49 and since then its been sitting in my closet because it does not accept any other network's sim.
aslezak said:
UPDATED USERDATA
Click to expand...
Click to collapse
That one don't work either
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
The problem with this seems to be, at least for me, that a .bz2 file is not recognized by the recovery as an installable zip.
The dd trick worked for me, but the system image here, is not full stock. IT seems to have a mix of super_su and magisk in it.
Root is working, but I can't seem to mount system as r/w
So trying to figure this out. I used this image to do a restore, and my phone was rooted with magisk.
First time a program tried root, it said that super su was installed. When I went to another one, it said that magisk was installed.
Anyrate, at one time I was able to mount system r/w and make changes. Now it seems that I can't for whatever reason. I don't know exactly how I got it
to the state to be able to modify the system.
I actually pulled an entire copy of the rom at one time, with a dd command. Of course that can't be reflashed from twrp. But I'd like to be able to mount it somehow on a pc so I could do a stringsearch for all files that have an ro, in them to find the master files where the filesystems are mounted, and edit those....
crashburn833 said:
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Click to expand...
Click to collapse
the system.img requires a monthly membership, could an updated link using something like mega or mediafire be created please?
one789 said:
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
Click to expand...
Click to collapse
what custom rom?
HELP PLEEEASE! Bricked h1711
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Hard bricked Dreaded QHSUSB_BULK issue. Need mmcblk0.img PLEASE PLEASE HELP!!!! I've lost recovery and fastboot! Nothing but a black screen and a blue light.
Click to expand...
Click to collapse
divineBliss said:
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Click to expand...
Click to collapse
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Whit3Rabbit said:
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
Click to expand...
Click to collapse
divineBliss said:
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Click to expand...
Click to collapse
That's what I was afraid of Thank you for the quick response.
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
Click to expand...
Click to collapse
What is the link to the info you found?
I have the image you need, but it is 15 GIGs in size, and there is no practical way to send that. I also have a system image, and a boot image with magisk in it, as per the OP.
P.M. me.
I don't see how you can recover this if you don't have recovery or fastboot, and can't boot into the phone. If the bootloader is corrupted, well I just don't know.
Can you get into twrp?
You do know that there are two recoveriess, one erecovery and another recovery.
It seems that POWER and VOL up may get you into one, and POWER and VOL down may get you into another one.
NOTE: I KNOW you can't flash the image via fastboot, cause I tried it. it is just to big.
The files are all to big to post here....
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 I put this up 6 days ago for someone else. I don't know how long the link is good for.
This is the system image from the non-working link. You will need to untar it.
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 <<<<<<<<<< file from Original Post
https://nofile.io/f/vTRffT3CM0s/erecovery.zip <<<<<<<<<< erecovery is same as stock recovery
https://nofile.io/f/3DRA4bYjdsq/twrp-xt2.7z <<<<<<<<<< Hweng's original twrp
https://nofile.io/f/uAET5bTqQVk/patched_boot.zip <<<<<< bootloader patched with magisk for a root that does not touch the system partition.
I'll try to put the 15 gig mmblockp0 up here if it will take it, but it is at the office.
I hope this helps.
I now also have a virgin system image, stock. The image given above appears to also have supersu installed it int.
at least it has a su in the system image. Where magisk, just patches the boot image as I understand it.
Any luck on that stock system.img? I formatted mine like an idiot and now sitting on a phone with no OS
same as above, i will even take the rooted system.img i have all other files needed.
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
littletech said:
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
Click to expand...
Click to collapse
step by step root > https://forum.xda-developers.com/hu...ooting-restoring-huawei-elate-h1711z-t3764391
the files for root are the same for the Elate and the XT2
Blue light black screen fix
Whit3Rabbit said:
That's what I was afraid of Thank you for the quick response.
Click to expand...
Click to collapse
My device suffered the same fate, only a blue light black screen unable to enter boot or recovery. I slowly removed the back cover using my fingernails and removed the two screws holding the metal plate above battery on the right. Popped the left most plug to disconnect the power flow and allow phone to power off completely. Be careful not to touch any of the metal near the plug or you will short. I plugged it back in and held volume down while I inserted USB connected to computer. Tada!! Back in action fastboot ready... So OK now what?? I can't seem to be able to flash an update. Zip just keeps saying failed to load, and system image is too big. Can someone point me to the correct files I need to get her working again? Thanks in advance.