Hello friends,
I've a problem with CWM 5.8.2.0. Until now I replaced with ease different ROM and went all right. But after the last one, system doen't reboot. Everything is installed properly, the system restarts properly with the factory image (eeepad asus Tegra etc..), but after few seconds it returns to the previous commands (reboot system now, install zip fron sdcard, wipe data and so on). I tried to restore the "old" ROM, all the step are complete, but I can't go further. The installation stop always after a few seconds. Thank you for your help.
How to Unbrick your Transformer Prime
"DiamondBack" discovered this, i tried it and it worked for me:
Don't be afraid, your Prime should be recoverable. This is the good news. The bad news is, that you need quite some knowledge of ADB.
To recover your Prime (most likely) you need the following:
A working ADB setup (please google that if you don't have it, "tutorial setup adb" or something like that should do the trick)
The USB-Cable to connect the Prime to your PC
A few minutes time
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
I Hope it helps!
Related
I can't seem to get the custom recover working on my eris. I followed the "adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
4. Close the command prompt and turn off you phone."
to the tee and everything seemed to work.I didnt recieve any error msg on the cmd console but when I boot up holding the Vol+ and power I get and Android under a ! in a triangle and a message that says "E:Can't open /cache/recovery/command then I only get 4 options and none of them are to flash a rom so I always reboot system. I really want to put a rom on here but I have no idea what went wrong. Im sorry if this is a redundant post. I combed a hundred of them and couldnt find anything like this. Thank you for any help in advance.
Oh and before I forget I tried the adb fastboot bootloader version as well. Everytime I do it it sits in the command console stating "waiting for device". Im plugged in so I dont understand what Im doing wrong.
Curious to know... are you using windows or mac? have you tried:
adb shell reboot recovery
to see if that does anything?
Maybe you have a different version of the recovery saved than I do, but mine is named "recovery-RA-eris-v1.6.2.img"...maybe you just had an input error somewhere along the line? forgot a capital letter or something? I had the same error myself and following the directions I got the recovery image back
Im running windows 7 and I have both recovery-RA-eris-v1.6.2.img and the recovery-RA-eris.img. I have been using the v1.6.2 and I just modify the command to look like this "adb push recovery-ra-eris-v1.6.2.img /sdcard" How would I use adb shell reboot recovery would I just sub that in place of something? kinda getting discouraged because I have tried this 10x now. I have checked and the usb debugging is on and I do have the eris 2.1 root and not the leak. I wonder is there any way I can flash this with something from the droid mkt place like SUFBS? Or maybe change a rom's name to look like an update zip?Just looking for ways to make this work Im so jealous of everyone that has got it to work.
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Dachix said:
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Click to expand...
Click to collapse
when hes saying fastboot will be highlighted in red he's referring to booting your phone into the standard recovery mode (when power is off) hold volume up and power.
Walking Taco seriously love that name. The only options I get when I hold down vol+ and pwr is 1. reboot system now 2. apply sdcard update 3. Wipe Data/ factory reset 4. Wipe cache partition and all are in purple and at the bottom on the phones screen is "E:Can't open/cache/recovery/command"
The website fuzz4net says to:
WINDOWS USERS
From your tools directory in the sdk do the following command
adb fastboot bootloader
You will have FASTBOOT highlighted in red like it is here
Now on your computer do the following
Fastboot flash recovery recovery-RA-eris-v1.6.2.img
Ok after that completes pull the battery then power back up with Vol Up + Power to enter recovery
But when I get done ...after the last step the cmd.exe window states <waiting for device> any ideas? Thanks for helping too. Leave it to me to hit a snare
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Dachix said:
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Click to expand...
Click to collapse
I honestly don't know man, I would factory wipe it and try and start from the beginning. I followed the fuzz's instructions and was rooted in less than a half hour. Sorry brother.
Thanks!
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Dachix said:
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Click to expand...
Click to collapse
Awesome news! Have fun with your rooted phone!
hi everyone,
I'm coming from this thread http://forum.xda-developers.com/showthread.php?t=1834761
I have been stuck for more than one week now and i didn't find any solution.
My problem is that I'm currently stock in a clockworkmod recovery boot loop on my Asus Transformer Prime without adb/fastboot connection:
1 - I had install CM9 stable on my Transformer Prime, after a wide data and then send throw "adb push" the CM9.zip,
2 - I reboot by CM9 in recovery mod to install Gapps,
3 - I install the Gapps zip,
4 - I ask to clockworkmod to reboot,
5 - Since then I'm in a clockworkmod recovery boot loop without adb/fastboot connection (witch used to be working),
If kown how can I get adb/fastboot connection back to be able to find my device with the adb command " adb devices " and then be able to send this command => " dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 "
Thank you for your understanding,
Kind regards,
Adb and fastboot are two different things... Fastboot is obtained buring booting process with vol down pressed, then not selecting recovery with volume up. So you should have fastboot access.
In this case I would suggest to fastboot flash TWRP (see on their website for instructions) it will perhaps fix things or at least give you adb access.
If you use cwm take the old 5.8.2.0 modded for not looping with reboot to recovery feature, or stay with twrp.
I would look at the following thread for unbricking the TF201:
http://forum.xda-developers.com/showthread.php?t=1514088
Sounds like you might fall into Option 1a.
I was having your same issue but it was because I rebooted into recovery from the reboot option on the CM10 rom. In any event, I couldn't get adb to work or recognize my device no matter what. I then decided to use my macbook pro. I can tell you that using adb on a mac is much easier as you don't have to download the drivers or sdk, just the platform tools. Here's a link: http://forum.xda-developers.com/showthread.php?t=1387527. I know this may not help if you or someone you know doesn't have a mac, but it saved me.
After searching and searching and searching I need to post a few questions.
I "accidentally" wiped the internal storage on my HTC One, and I have been trying to side load a new rom for 3 hours with no luck at all.
I hit adb sideload in TWRP it just sits at starting adb side load feature... and does nothing.
On my mac I have ADB installed and it pops up as usual in a terminal window, but when I search for devices, it shows no devices found.
Any suggestions other than to search the forums, because I have had no luck.
allhailcardiel said:
Hopefully this thread can be moved then.
Yes, I have the phone in recovery when searching.
that is really all I can do with the phone currently is boot to recovery.
Click to expand...
Click to collapse
I'm not familiar with Mac and what you need. Did adb work before on that Mac with your HTC one?
Sent from my HTC One using Tapatalk 4
xcrazydx said:
I'm not familiar with Mac and what you need. Did adb work before on that Mac with your HTC one?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
allhailcardiel said:
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
Click to expand...
Click to collapse
Glad it worked, I don't use Mac so I didn't know what all was needed to run adb or if you had it working previous to the wipe.
Sent from my HTC One using Tapatalk 4
allhailcardiel said:
After searching and searching and searching I need to post a few questions.
I "accidentally" wiped the internal storage on my HTC One, and I have been trying to side load a new rom for 3 hours with no luck at all.
I hit adb sideload in TWRP it just sits at starting adb side load feature... and does nothing.
On my mac I have ADB installed and it pops up as usual in a terminal window, but when I search for devices, it shows no devices found.
Any suggestions other than to search the forums, because I have had no luck.
Click to expand...
Click to collapse
I doubt you will ever wipe your internals again after this experience, but its always good to have an OTG cable that you can buy online for like $3.. You can install from usb flash using this cable in twrp recovery like its an external sd card. Its also useful for other simple transfer type of work.
Thread has been moved to Q&A. :good:
Help me
allhailcardiel said:
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
Click to expand...
Click to collapse
Hey man, I am on the same boat right now. Can you please tell me the exact steps you took to recover?
I am fairly new at this and kinda freaking out.
Thanks.
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Danvid113 said:
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Click to expand...
Click to collapse
PHP:
Having same problem. Did you have to install eclipse or can i just install sdk?
lankyboy29 said:
PHP:
Having same problem. Did you have to install eclipse or can i just install sdk?
Click to expand...
Click to collapse
Just the sdk. At least for me it worked ok
Danvid113 said:
Just the sdk. At least for me it worked ok
Click to expand...
Click to collapse
PHP:
ok i got through the side load steps. I did the side load yet on my phone it does nothing while in side load mode that is. Does it supposed to say anything once I side load the .zip or do I just hit cancel after and reboot.
Thanks.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
Do you know what mount does? because only data and cache were selected. do i need system checked as well?
lankyboy29 said:
ok i got through the side load steps. I did the side load yet on my phone it does nothing while in side load mode that is. Does it supposed to say anything once I side load the .zip or do I just hit cancel after and reboot.
Thanks.
Click to expand...
Click to collapse
ok, so what should happen is that your computer shows that it is transferred. After it is done, your phone should install the program. Sometimes it doesn't show anything for me. These times i just wait until something happens, if still nothing either hit cancel or back. It worked for me every time; if you still have problems, you should upload a video of the whole procedure, so I can have some idea of what is going wrong (send a youtube link in pm)
Danvid113 said:
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Click to expand...
Click to collapse
Thank you so much for this ,,i tried everything with no success. This worked for me.You are the best. Im bookmarking this so if it happens again. Bang I know where to look.
I'm also using Mac (10.9.x) and had the same problem - accidentally wiped my HTC One sdcard and had no ROM, nothing and sideload didn't work (when I give the adb sideload command in terminal, it exits within a few secs and nothing changes on the phone).
The quickest solution for me was to just stay in TWRP with USB connected and....
1) Manually copy the ROM binary in terminal ie. :
adb push <path_to_ROM> /sdcard/
2) After above completes, in TWRP, just select "Install zip from sdcard" and select the file copied above from /sdcard/
Your description worked for me. Thanks you!
But I also had issues with adb . If anyone ever looking for a solution go to stackoverflow and search "Installing ADB on MAC OS X"
and then apply Danvid113s solution.
xcrazydx said:
Glad it worked, I don't use Mac so I didn't know what all was needed to run adb or if you had it working previous to the wipe.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Im on the same boat. what did you do exactly?
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Dexter885 said:
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?t=2439949.
It seems that the bootloader is locked.
tylerr55 said:
Look here: http://forum.xda-developers.com/showthread.php?t=2439949.
It seems that the bootloader is locked.
Click to expand...
Click to collapse
If overwriting / dev/block/mmcblk0p5 with emmc_appsboot.bin, the phone will not boot up. It must be restored with an image kdz.
Any news? I've been waiting for cwm for long
Hey,
The correct comand on adb to unlock bootloader on Lg devices is:
adb reboot oem-unlock
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
reffer to http://forum.xda-developers.com/showthread.php?t=2224020
pedrocel85 said:
Hey,
The correct comand on adb to unlock bootloader on Lg devices is:
adb reboot oem-unlock
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
reffer to http://forum.xda-developers.com/showthread.php?t=2224020
Click to expand...
Click to collapse
Someone try this method on P710?
try, it will do no harm
maxx_hr said:
Someone try this method on P710?
Click to expand...
Click to collapse
Did you try it?
Did it work?
======================
OP:
Dexter885 said:
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Click to expand...
Click to collapse
Any news about the recovery?
Vagelis1608 said:
Did you try it?
Did it work?
======================
OP:
Any news about the recovery?
Click to expand...
Click to collapse
Tried, does not work!, Googling I found this guide,
Code:
://translate.googleusercontent.com/translate_c?depth=1&hl=it&rurl=translate.google.it&sl=ru&tl=en&u=http://4pda.ru/forum/index.php%3Fshowtopic%3D466295%26st%3D0&usg=ALkJrhhM8yja33NUhK__pNP0aLRznOSGhg#entry22312158
But it not work well on the P710. I found this bug: when you disconnect and reconnect the battery the phone will not turn over and go into an infinite loop!
Necessary to crack the bootloader, but I nn I know these ...
The cwm start on my lg p710 but the same problem with battery,if i go in cwm(volum down+home+power)and rebot from there the phone start.
Sorry for my bad english.
I try CWM from this thread:
http://forum.xda-developers.com/show...2700579&page=3
on my P710, and it works-no upside down problem, no bootloops.
But I dont install gscript, just put APPSSBL.bin and recovery.img on their places.
After that, i perform backup with one warning message-no file_contexts, but on second backup it dissapears...:good:
nobody here still unlocked L7 II bootloader ?
please take look at this
http://forum.xda-developers.com/showthread.php?t=2212092&page=4
since page 4 there are users talking about unlocking bootloader and it seems some of them did unlock bootloader and installed succesfully CWM.
RenatoNismo said:
nobody here still unlocked L7 II bootloader ?
please take look at this
http://forum.xda-developers.com/showthread.php?t=2212092&page=4
since page 4 there are users talking about unlocking bootloader and it seems some of them did unlock bootloader and installed succesfully CWM.
Click to expand...
Click to collapse
Just see link from my post, this is newer version of your, taken from same russian site.
With this bootloader and CWM, i just flash some P713 mod (deodexed, with kit-kat look), but i can confirm some problem with restoring-everything works, but restoring data (maby because i have more than 500 files in one folder ) failed. I must try restoring without that amount of data.
Anyway, backup in my case, is success, because restoration of sistem/boot gives me result like factory reset of original (but some data, before error is restored). After restoring, i just reset/clean dalvik to clean garbage, and phone works like new one, and even stay rooted.
Sorry for bad english...
Hey guys, I'm using asus ZenFone 2 with lineage os. Actually I got stuck with Twrp Bootloop. First I tried the dd command "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/misc count=1 bs=32" and it broke the loop and it booted to the os. But after a couple of restarts it again went to the loop. I tried the same command but it didn't work, so I tried to use another command which I don't remember now and when I rebooted it my asus logo changed to some colour panel, now it is not booting to recovery. I'm stuck with boot loader. I tried to use adb shell command but it mentioned as "devices null" but when I try the "fastboot reboot" option it works. Please help me with this huge problem. :crying: