Related
ph84 said that dual boot is possible and he will write how to.
When???(don't hurry, I only ask)
Maybe your question can be answered if you look for the Topogigi's post in this thread [HOW TO] Linux on Folio.
I've not try this, because i don't understand some things... if someone makes a how to step by step, would be amazing !!
Here is how to get it without steps:
Topogigi said:
[ONLY FOR DEVELOPERS AND SKILLED PEOPLE: NOT FOR NEWBIES!!!]
My 2 cents:
I installed ubuntu and it works quite well. I'd like to point out that it you can boot android or ubuntu flashing the boot.img containing the linux kernel in place of recovery kernel (fastboot flash recovery boot.img). You can even try a kernel before flashing it to the device (fastboot boot boot.img). To enter fastboot mode in your device, simply press the power button three times when the Toshiba logo appears on the screen at powerup, then press volume up one time. Voila, you are in fastboot mode...
To boot linux, you have to press "power+volume up", then follow the instruction on screen to wipe the device (don't worry, it will boot linux and it will not wipe anything). You'll miss the recovery partition that way, but you'll gain a dual-boot tablet with android and ubuntu in change. Not a bad trade.
If you really need recovery, you can always reflash it with fastboot, so the process is perfectly reversible.
Now, back to business:
1) Touchscreen works (sort of). If you apt-get evtest, you'll notice that /dev/input/event3 is bound to the touchscreen and it reports to be alive and kicking. The test reports the coordinate changing and the pressure on the screen (multitouch works too). But......in Xorg, the device only reports the pressure and coordinates are not changing. You can test with xinput as I did. It seems a software-related issue: the drivers does not report correctly what the hardware is telling him. I'll investigate and report back if news will come out.
2) Wifi could eventually work. The card is bound via SDIO bus, and a ar6000 driver supporting SDIO is available. I'll try to compile the driver ASAP.
3) Suspend, cpufreq do not work and I doubt they will work without driver sources
4) Battery is working, framebuffer is working good and the system seems quite snappy also with an EXT4 partition on a MMC. Openoffice works great, quicker than expected.
5) If you compile the kernel with nilfs2 support, you can easily mount all the android partitions within ubuntu with ease. Not bad...
That's all for the moment: I hope that someone will help me to make this little devil fly.
Click to expand...
Click to collapse
sergi711 said:
Maybe your question can be answered if you look for the Topogigi's post in this thread [HOW TO] Linux on Folio.
I've not try this, because i don't understand some things... if someone makes a how to step by step, would be amazing !!
Here is how to get it without steps:
Click to expand...
Click to collapse
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Akta77 said:
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Click to expand...
Click to collapse
It sounds easy... but i have never enter in fastboot mode... I don't know what commands use...
Another question, I have flashed the update.zip from ph84 to boot only ubuntu, when i flash this boot.img on fastboot mode how I flash the foliomod ???
fastboot, SDK, UPDATE.ZIP, DRIVERS etc.
Sergi711
1.I know for that(try), but I can't use fastboot. I installed all drivers, but I can't send commands to Folio 100. I made thread for help, but no one help me. If you can help, please, help me!!!!!!
Can we make update.zip with that kernel and don't use fastboot?
2.a)First, download and install SDK.
http://developer.android.com/sdk/index.html
Second, go here http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets and install drivers.
Third, enter fastboot mode(3X Power UP+Volume UP) IF YOU PRESS POWER UP 4X, YOU'LL BRICK TABLET AND FOR THAT YOU CAN'T FIND HELP!!!!!
Moreover, connect Folio with PC,Laptop, NetBook, Tablet PC or NoteBook via USB and open terminal(Start>Run>cmd) and go to C:/android-sdk/platform-tools (in my
case)
Terminal: cd C:/android-sdk/platform-tools
Fifth, now run fastboot.exe and type anything you want
Terminal: fastboot _______________( fastboot flash recovery boot.img)
b) If you flash boot.img from ph84 to boot Ubuntu ARM on Folio 100, in future, you'll can only boot from SD Card or USB(sdmmc-update.zip or usb-update.zip). You'll not use Folio's internal storage and you'll can't boot to FolioMod, but from recovery you can easily reflash FolioMod or another rom or custom kernel(you need to reflash kernel and you can made your own update.zip with your custom kernel and don't touch FolioMod )
Akta77
Can we we copy recovery to /date or /date/date folder and boot it like MCLP said for installing FolioMod or another rom?
Step 1. Install Root Explorer on Folio 100(can't post app, because rules, but with googling find it easily or download it from android market)
Step 2. Copy the recovery image from FolioMod(if you want original recovery) or from CyanogenMod7.0.0(if you want unofficial ClockworkMod recovery) to SD Card or Internal storage
Step 3.With Root Explorer copy recovery.img to /date or if you find another date directory inside copy there(copy recovery.img to both directory just in case)
Step 4. Exit from Root Explorer, got to Settings>Applications>Development and enable USB Debugging
Step 5. Connect Folio 100 to PC or etc. via USB and open Terminal(cmd) and go to SDK directory C:/android-sdk/platform-tools(in my case)
Terminal: cd C:/android-sdk/platform-tools
adb shell (use this if you have installed SDK drivers for Tegra devices)
cat /data/recovery.img >/dev/block/mmcblk0p7
or
Install any Terminal app on Folio 100 and type
Android Terminal: cat /data/recovery.img >/dev/block/mmcblk0p7
After this, you should have recovery
Jon2555 said:
Sergi711
1.I know for that(try), but I can't use fastboot. I installed all drivers, but I can't send commands to Folio 100. I made thread for help, but no one help me. If you can help, please, help me!!!!!!
Click to expand...
Click to collapse
Maybe this helps: http://forum.xda-developers.com/showthread.php?t=1055754
Most other fastboot binaries out there don't recognize tegra devices.
I just use the SDK's Fastboot under Linux (built from Cyanogen's 7 repo) without any problem.
If you are using Windows, have you modified the inf has stated by google?
Entering fastboot is simple : just press x3 power and then volume up at boot screen.
You will be in fastboot mode.
I am not sure we can boot the kernel from somewhere else than boot partition or recovery partition. But we could maybe build a relocable kernel and load Linux or Android using kexec from boot partition like "petiboot" on PS3
Akta
Thank's guys!!! I'm going to try it whan I back from France.
Sent from my folio 100 using Tapatalk
could someone that have a dual boot ubutntu/android make a how to for us... ??? because i read the lastest post that you reply i don't know how to have a dual boot yet.. i can't understand... please a how to is needed, step by step...
thanks in advance !!!
Hi,
Just wrote you how to do it
Boot the tab in fastboot (3xPower + 1 Vol Up)
Then connect your tablet on your PC and do :
fastboot flash recovery boot.img (boot.img is extracted from update.zip according to your wish (SDCARD or USB PENDRIVE)).
Akta
ok i flash the boot.img on fastboot, and then ??? i only have now ubuntu, how i install android after fastboot flash boot boot.img ????
I know, i must enter fastboot mode, and flash boot.img instead of recovery.
After that, i will only be able to boot from sdcard... isn't it ?
Ok, i must have 2 sdcards to boot android, and the other sdcard to boot ubuntu ???
if this is right... how the sdcard must be ??? update.zip on the root ???, the update zip extracted on the root of sdcard ??
i have lot of doubts after the fastboot flash recovery boot.img step, sorry.... can anyone help me ??
I think when you flash boot.img(sd or usb) for dualboot, when sd card with Ubuntu is in Folio you'll boot ubuntu(sd or usb) and if you haven't got Ubuntu sdcard or you have it (but not Ubuntu sd) or if you haven't any you will boot to android.
What's up with my question?
Sent from my folio 100 using Tapatalk
Ok i understand that after flash boot.img instead of recovery on fastboot mode... folio will boot from sdcard, in that case, if you push a sdcard with an ubuntu filesystem, folio will boot ubuntu, and if you remove sd after boot moment, folio will recognise internal sd and boot android ??? thats it ???
edit: but what boot.img must i flash ???
When i will have some time, i will rebuild a boot.img able too boot linux from a second partition on the sdcard. You will have fat32 on first partition and ext3 or ext4 on second. For now, you can live your sdcard in the folio but android is not able to access it (lack of ext3 / ext4 support, but easy to install ).
Akta
Thank's Akta for your help!!! Can you sometime post your progress? I want to help, but I don't have dev skills. Can you post some good link(searched, but no luck) or your howto about making kernels? I found for themes and I'll try to make some in my free time.
Sent from my folio 100 using Tapatalk
Quite interested by the dual boot on Folio 100.
I will keep an eye on this thread.
Akta77 said:
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Click to expand...
Click to collapse
I there, I have few questions:
First, why are you flashing boot into recovery? Is not supposed that boot is the image that cares about booting procedure?
Second, once first question is solved, which boot image are we supposed to flash? I mean, we will need one that searches into sd for a boot/grub, isnt it?
Third, what about the procedure, I explain myself, the logical order of doing all this is: flash an android rom, CM for example, then do the procedure to install ubuntu into the sd and finally flash the boot img so system looks for sd-ubuntu and if it's not found, then boot internal android rom, am i right?
Thanks!
1. Yes.
2. Yes.
3. Yes.
Sent from my GT-I5700 using Tapatalk
Well, then:
Which image should we flash? Where can I can get it?
And finally, this image where must be flashed to dualboot?
Thanks!
Look in the second post on first page. You will see someone talking about dual boot. Find that post in first threde of Ubuntu for Folio 100 that wrote DerArtem(I think)
I don't have time to post link, but if you don't find it tell me and I'll post link.
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
kevinb77 said:
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
Click to expand...
Click to collapse
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Gage_Hero said:
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Click to expand...
Click to collapse
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
kevinb77 said:
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
Click to expand...
Click to collapse
Did you ever have any luck with this? I had a JB ROM soft brick my 201 about a year ago. I lost TWRP recovery, OS, pretty much everything. It stays on the splash screen and allows me to get to the fastboot option. I can't get my computer(windows 8) to recognize it at all. Just states it can not recognize USB device. I installed the universal naked driver package along with trying the stock ASUS driver package with no luck.
I put the tablet down and purchased a 701 but now would like to fix the 201 and sell it. If you have any advice I would be very thankful
Hi,
l'm really need HELP desperately to update my folio 100 from factory installed 2.2.15 version to the latest jellybean. l have rooted my device using Superone-click, installed the necassery andriod SDK/adb /PdaNet drivers, tested that the device is rooted using Terminal emulator. But l cant update the recovery or install a new ROM, have tried everything l learnt from this site including install update.zip from SD card , fastboot recovery to install custom recovery,everything just won't work apart from the device being rooted. Here is the error l get after l tried to fastboot a new recovery image from my PC to my tablet : "erase recovery failed(write command failed)too many links))", but suprisingly l can fastboot reboot the tablet from my pc. :THIS IS THE ERROR FROM MY TABLET DURING FASTBOOT mode: Failed to process command getvarartition-type recovery :recovery error(0x2) .[/COL PLEASE HELP, Been at it all week,l'm primarily a windows user.
Same problem here!
Already solved. The problem was that the fastboot didn't detect my tablet. When I do fastboot devices, it replys: ? fastboot.
With adb everything is OK!
On fastboot commands erase, flash etc, nothing was working. Except reboot.
The only way was: fastboot boot recovery-cwm-CM10-A3.img [/B](Have to be on your Pc fastboot directory) and then install everything from SD card.
Note: I can't intall recovery yet, give me an error 7 or something. Everything else is fine, and the rom is realy awsome Thanks!
rastonb said:
Already solved. The problem was that the fastboot didn't detect my tablet. When I do fastboot devices, it replys: ? fastboot.
With adb everything is OK!
On fastboot commands erase, flash etc, nothing was working. Except reboot.
The only way was: fastboot boot recovery-cwm-CM10-A3.img [/B](Have to be on your Pc fastboot directory) and then install everything from SD card.
Note: I can't intall recovery yet, give me an error 7 or something. Everything else is fine, and the rom is realy awsome Thanks!
Click to expand...
Click to collapse
Same problem here but i had already recovery-cwm-6.0.1.4 and A2 on my folio. So I installed until A5 with this recovery without problems.
RE:Q] [q] help:problem updating/fastbooting toshiba folio 100
acilo said:
Same problem here but i had already recovery-cwm-6.0.1.4 and A2 on my folio. So I installed until A5 with this recovery without problems.
Click to expand...
Click to collapse
How were u able to install recovery-cwm-6.0.1.4 and A2 on your toshiba folio 100
TEEBOYZ said:
How were u able to install recovery-cwm-6.0.1.4 and A2 on your toshiba folio 100
Click to expand...
Click to collapse
I did it how it is discribed for "Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012" in this post: http://forum.xda-developers.com/showpost.php?p=31004271&postcount=9.
My former FW was foliomod1.4.
rastonb said:
Already solved. The problem was that the fastboot didn't detect my tablet. When I do fastboot devices, it replys: ? fastboot.
With adb everything is OK!
On fastboot commands erase, flash etc, nothing was working. Except reboot.
The only way was: fastboot boot recovery-cwm-CM10-A3.img [/B](Have to be on your Pc fastboot directory) and then install everything from SD card.
Note: I can't install recovery yet, give me an error 7 or something. Everything else is fine, and the rom is realy awsome Thanks!
Click to expand...
Click to collapse
l did as you suggested, was able to fasboot into recovery, installed formatsd, cm-9.0.0-RC0-2012.03.04-betelgeuse-KANG-signed and goggle apps, wiped cache/data and reboooted, but the new image won't boot up, will like to know what steps you took,/how you were able to successfully load the image and which image did you use...THANKS
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?
Hi all. Before i start i want to say, i read a lot of threaths and comments before i started to booting recovery and i followed Tutorial that you can find somewhere here on XDA for MotoE.
I unlocked Bootloader correctly and everything was right. Then i downloaded latest version of TWRP and CWM if something will be wrong.
So i booted into bootloader, connected to PC (windows 8.1) and using adb i installed TWRP (by command window). After instalation was complete, i used comand: "fastboot reboot" to get my mobile start normally. Everything worked fine so i started last step. Turned off mobile, booted into bootloader(or maybe fastboot? idk...) and by volumebuttons i choosed "Recovery" . Then a black screen for a minute. After that mobile stuck on screen that i attached down below. So i tried this but with CWM (same process way). But nothing new... Someone said me i had to try "Minimal ADB and Fastboot" but again, nothing happend.
Can you help me guys?
The recovery isn't installed! Reinstall the recovery and follow correct steps!
I tried it one more time. I´m attaching image that is from command window showing that .img was booted ... Strange is, immediately after booting was completed, mobile restarted... and after i turned off mobile again, still i can´t reach recovery. Isn´t that problem in .img file? maybe it´s broken, isn´t it?
Tried once again
Ok last try didnt worked. So i complettly followed this guide http://forum.xda-developers.com/moto-e/general/guide-one-moto-e-beginners-guide-t2807891 STEP-BY STEP!
Command window screen attached, Fastboot screen attached.
After reboot, turn off i tried to open recovery and again that image that i posted in first coment. (android figure with words: no command)
By that guide i downloaded recovery from here: https://goo.im/devs/OpenRecovery/condor/
and i downloaded just "openrecovery-twrp-2.7.1.0-condor.img" as i have to do it (written in guide)
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
neo.ank said:
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Mondop said:
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Click to expand...
Click to collapse
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
neo.ank said:
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
Click to expand...
Click to collapse
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Mondop said:
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Click to expand...
Click to collapse
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
neo.ank said:
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
Click to expand...
Click to collapse
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Mondop said:
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Click to expand...
Click to collapse
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
neo.ank said:
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
Click to expand...
Click to collapse
Okay, can you give me link with tutorial? i found just this one which restores whole system (and its 4.4.3 and i have now 4.4.4, i mean this will be maybe problem, wouldn´t it?)
i mean this one (tutorial how to restore moto E)
http://forum.xda-developers.com/showthread.php?t=2759495
did you try updating / reinstalling USB-driver on your computer?
magicw said:
did you try updating / reinstalling USB-driver on your computer?
Click to expand...
Click to collapse
no i didnt, think you it will help? i mean if i can connect my mobile into pc without any problem in normal mode and in fastboot too... i will unninstal drivers, intall them again and them i will try unninstal motorola device manager and then again intall him.
(i had newest drivers i can update them)
LOL?
OK im in recovery i already flashed superSU...
What did i do?
As you said, i reinstalled all drivers...
then i downloaded same TWRP again (but with mirror source)
I downloaded attached md5 file ( still dont know what should i do with it )
moved recovery and .md5 files into minimal adb and fastboot (both files i renamed to "recovery")
turned off devices
started fastboot
connected to PC
started command window and entered command "fastboot flash recovery recovery.img"
then i didnt wrote sommand "fastboot reboot" as i done before
i just unpluged usb and navigate to recovery button and launched it
and VUALA im in recovery
hurraaa
just installed superSU and then rebooted.
everything works (superSU too)
i have one more question...
i downloaded twrp manager from google play
first start: asked for root permission a allowed it
then message appeard:
"The only compatible version of busybox we support is Stericson. All other cause havoc on all operations in this app. Please click yes to install Stericson busybox"
what the heck is busybox?
+Should i download it or not?
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
ok then
magicw said:
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
Click to expand...
Click to collapse
i have no reason to want twrp manager, i just wanted to look at this app, and i found that busybox there so i wanted to ask here
thx for answer, now i undertand