Related
Hi, I accidentally wiped my SD card in TWRP, and I held the power button in an attempt to stop it. That of course didn't work, and my SD card was unusable. So I tried partitioning it with TWRP (Advanced > Partition SD Card) and that didn't do anything. I plugged it into my PC running Ubuntu 11.04 and formatted it to Fat32, and I'm now able to copy files to it and such with my PC, but I can't flash anything from it, and I have no ROM currently installed on it. I need help getting the SD card working again.
Do you still have TWRP recovery installed? If you do, boot to it and post the result of the following...
Code:
adb shell
parted /dev/block/mmcblk0
unit
^This will ask for another input. Type "B" and hit Enter
print
This will show your current partition layout.
Code:
print
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734296576B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 2041053183B 1192230912B ext4 userdata
11 2041053184B 2309488639B 268435456B ext4 cache
12 2309488640B 7689732095B 5380243456B media
It's showing that the "media" partition (sdcard) isn't formatted to fat32.
You would have to reformat it from TWRP recovery. The following should work.
Code:
adb shell
parted /dev/block/mmcblk0
mkfs 12 fat32
^This will format partition 12 to the fat32 filesystem.
lmntone said:
It's showing that the "media" partition (sdcard) isn't formatted to fat32.
You would have to reformat it from TWRP recovery. The following should work.
Code:
adb shell
parted /dev/block/mmcblk0
mkfs 12 fat32
^This will format partition 12 to the fat32 filesystem.
Click to expand...
Click to collapse
Thank you so much, that fixed it.
FroyoShark said:
Thank you so much, that fixed it.
Click to expand...
Click to collapse
Glad to hear your KF is back to normal.
Missing partition 11 and flag msftres on partition 12
Hello, I have rooted my kindle fire and i tried to partition it with FireParted and it unsuccessfully parted. Here are the partition details:
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734296576B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 2041000447B 1192178176B ext4
12 2309488640B 4309000191B 1999511552B fat32 media msftres
Please help thankyou
the simpliest way should be to use fff version 1.1 or higher
boot to fastboot mode and issue "fastboot oem format"
http://forum.xda-developers.com/showthread.php?t=1369405
this should restore the factory partitioning
RE:
It says
. . . FAILED (remote failure)
finished. total time: 0.004s
is your fff version 1.1 or newer ?
twrp installs version 1.0
would suggest to install (linked in) version 1.2 and retry
RE:
I downloaded FIREFIREFIRE 1.2 boot loader
And when i did the fastboot command it worked
Thanks for the input!
glad to help ...
Perfect fix!
Using Android's parted via adb shell as described in this post worked like a charm. I had tried to reformat the sdcard partition from both linux (using gparted) and windows 7, to fat32, but still couldn't get it to mount within android even though I could mount the partition as USB using TWRP or CWMR. But parted via adb shell was the ticket to success! THANK YOU!!
I essentially have the same issue, but cannot get my KF to connect for ADB to run the commands. Seems that when I put the Energy ROM (latest) on it, it now identifies itself as an "Am" in the device manager and no matter what I do I cannot get the drivers to install for it.
The only thing I was able to do successfully is use the KFU to set bootmode to Fastboot if I have it waiting to see device and restart it. There is a brief moment of connectivity but that is it.
My device would work fine if I could get the SDcard portion properly configured/formatted. This all stems from really bricking it good trying to flash the newest Kernel and everything went south.
Any suggestions? Plain english please as I am very novice.
When I mount normally out of twrp it comes up am if I mount SD in twrp it comes up kindle I wonder if this doesn't point straight to your USB mass storage drivers
---------- Post added at 08:23 PM ---------- Previous post was at 08:11 PM ----------
This is what I would do you have choices I think.
1. Unplug your kindle and restore your computer with system restore to an earlier time when the drivers were good then plug your kindle in while in twrp to see if there is any change in adb or mass storage.
Or 2. Startup the kfu and run the driver file to then check device status to see if adb is back online.
Or 3 without your kindle plugged either run driver install then plug in check for a change or go through the process of manually installing your drivers.
---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------
Edit wait I will look up another post standby
---------- Post added at 08:41 PM ---------- Previous post was at 08:26 PM ----------
http://forum.xda-developers.com/showthread.php?t=1625356 OK start here in about 8 hours I will post what I did when I'm at my computer
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
The driver needs to be edited and reinstalled to use adb on the newer roms.
I had to add
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_021&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
to [Google.NTamd64] and [Google.NTx86] in android_winusb.inf before it would recognize the drivers, but after that it worked.
I opened the inf. file with notepad copied the two line code above set my cursor just after [Google.NTamd64] hit enter right clicked pasted the code did the same thing after [Google.NTx86] saved the notepad file. This was all within the provided files in the kindle fire utility. Then ran the driver install disregarded the warning ran it anyway. Giving me working adb
Thanks so much! With a little doing, it finally worked! Once I got the drivers to connect to my device again by adding those lines it made it possible to communicate with it again and get it fixed.
Now, being hooked on this stuff like the rest of you... I may have to change ROM's again to take advantage of the new Kernel with all the fixes for the annoyances.
Hope I don't brick it again. lol
Me too your welcome
Broken SD
Hi. i have partitioned my Scard using TWRP. butt my battery comes down, and phone off.
Now i cannot use my SD Card, in phone i cannot see it. in Windows PC too. Like unconnected.
I have searched in device manager, butt cannot see there my card, no RAW partition. another sdcard works good.
Is my SD Card only software-demaged using TWRP, Or it was hardware-broken by another cause?
gouster3 said:
Hi. i have partitioned my Scard using TWRP. butt my battery comes down, and phone off.
Now i cannot use my SD Card, in phone i cannot see it. in Windows PC too. Like unconnected.
I have searched in device manager, butt cannot see there my card, no RAW partition. another sdcard works good.
Is my SD Card only software-demaged using TWRP, Or it was hardware-broken by another cause?
Click to expand...
Click to collapse
The kindle fire 1 doesn't have a removable SD card.
Sent from my XT907 using Tapatalk
Using KFU v0.9.8 this evening, I was able to install TWRP v2.4.4.0 and FFF on my 1st gen KF, as well as to root it and install the GO launcher. I'm now interested in installing JB 10.1.
Before I do, however, I want to backup the device Using TWRP's backup feature, I am able to get to the point where it has backed up all 6 partitions. However, it appears to hang at "Updating partition details..." with the words "Generating MD5" at the top of the backup window. FWIW, I have tried it without MD5 and the same problem still happens but then it says "Backing up Android Secure" at the top.
Any ideas what may be causing this and a possible workaround? I'm hesitant to believe this backup will allow me to recover the KF later if needed.
Any advice is appreciated.
Many thanks,
Mumford67
Run smirkit and flash COT Recovery instead of twrp and your issues will magically disappear.
Sent from my Nexus 7 using Tapatalk 2
asf58967 said:
Run smirkit and flash COT Recovery instead of twrp and your issues will magically disappear.
Click to expand...
Click to collapse
That worked perfectly! As it is, came to realization that KFU had never installed Superuser privileges anyway. Had to readjust the batch file to allow enough time for the Kindle to reboot so that it could install Superuser.
Now I'm running with CM's latest Jelly Bean build and all is wonderful!
Thanks for the help!
Mumford67
Same boat but your solution is beyond my experience
Original KF, 6.3.2, KFU 98+, TWRP v2.4.4
I'm in the same boat, stuck at stuck at "updating partition details" TWRP v2.4.4 after seemingly successful backup.
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
I really need some help, thanks
---------- Post added at 09:34 PM ---------- Previous post was at 08:55 PM ----------
mebobbob said:
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
Click to expand...
Click to collapse
I grabbed my kahonas and just forced a reboot. No idea if the backup is any good, not gonna risk finding out. I sideloaded superuser.apk from KFU folder and that went fine, got my root access.
My objective was simply to get root and backup apps+data for my kids' games before loading jellybean. So far so good...
mebobbob said:
Original KF, 6.3.2, KFU 98+, TWRP v2.4.4
I'm in the same boat, stuck at stuck at "updating partition details" TWRP v2.4.4 after seemingly successful backup.
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
I really need some help, thanks
---------- Post added at 09:34 PM ---------- Previous post was at 08:55 PM ----------
I grabbed my kahonas and just forced a reboot. No idea if the backup is any good, not gonna risk finding out. I sideloaded superuser.apk from KFU folder and that went fine, got my root access.
My objective was simply to get root and backup apps+data for my kids' games before loading jellybean. So far so good...
Click to expand...
Click to collapse
Post back if you need help with anything.
Sent from my Samsung Galaxy SV using Tapatalk 3
I'm going to update KFU with more time to upload superuser and I will add an option for COTR. Hopefully I will see less problems like this.
Sent from my One V using xda app-developers app
thanks for continuous development, winging it for now
awidawad said:
I'm going to update KFU with more time to upload superuser and I will add an option for COTR. Hopefully I will see less problems like this.
Click to expand...
Click to collapse
being a half-assed informed newb I used KFU to install COTR by renaming the COTR img to twrp.img in the KFU recovery folder [made a twrp.ori]. COTR installed and did the trick so now I have a couple of different configurations/ROMs backed up to toy around with.
I'm sure if I took more time to learn how it all works there'd be a more straight forward way, but... haha
I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")
scalywhisper said:
I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")
Click to expand...
Click to collapse
To force reboot hold down the power button until it shuts off then power it back on. Also, if SU wasn't installed then boot to TWRP, the under the reboot menu select system and if SU isn't detected it will install it for you. Good luck!
Sent from my One V using xda app-developers app
here's everything i did, going fine now
scalywhisper said:
I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")
Click to expand...
Click to collapse
Generally, I had issues using the KFU 98+ but nothing insurmountable and definitely got everything done that i couldn't get done before!
Follow the KFU/TWRP instructions carefully, as i assume you've done.
Once you run KFU to install SU, your Fire is "ready" to be rooted even if it didn't install the SU app/apk. If you don't have root after running KFU, you can still sideload superuser.apk. With your Fire connected to your PC and ready for file transfers, copy superuser.apk found in KFU\files\ to your Fire. On your Fire, disconnect USB, browse to where you saved superuser.apk and install it. Run the app to establish SU access. Your rooted. Use a rootchecker app to confirm if you need to.
When I got stuck in TWRP, I forced shutdown by holding the power button until it turned off. When i powered back up, it booted fine all the way to Fire home screen. I had a backup of unknown quality because i was unsure if it finished.
To get a good backup, I used COTR [Cannibal Open Touch Recovery], found here
There's nothing wrong with TWRP, it's what I've used before but v2.4.4 simply wasn't reliable for me. The half-assed-but-worked-anyway method for me was installing COTR by using KFU. On your PC, in the KFU folder \recovery\, change the twrp.img to twrp.ori. Copy the COTR image into the same \recovery\ folder [CannibalOpenTouch-v2.1_otter.img downloaded from above link]. Change the COTR filename to twrp.img.
Now, with your Fire connected to PC, Run KFU and install TWRP - it will actually install COTR.
Now reboot your Fire to recovery, same method as you did for TWRP. Use COTR to run Nandroid [standard android backup tool]. works perfect.
This sounds really complicated but it really isn't too rough. Be patient, lots of reboots.
The backups are found in a \cotrecovery\ folder on your Fire. I copied them to my PC for safe keeping. I was able to go back and forth between original setup and new reset configuration fairly easily until I had everything the way I wanted.
To prevent Amazon from updating your fire and taking root away, see this article.
I did all this just because I screwed up my parental access PW on my Fire! only way around that is to reset to factory defaults. I wanted to backup app data [games and a few critical apps] to reload after reset. My kids would have been heartbroken to loose all their progress on a few games and I felt like an idiot for screwing up the password. all said it was worth it to restore root [lost it way back after an update]. I used Mybackup Pro to save apps+data online, GREAT app [requires root to save app data]. Its a regular app you run from Fire home and you can very selectively pick what apps and data you want to backup. Not the same as recovery mode backup, such as TWRP, COTR, or clockwork.
Good luck and I hope this roundabout method helps you if you're still stuck. While i was at it, i tried a few ROMs with ICS and Jellybean but didn't really like them on my Fire and really wasn't up to figuring out how navigate the systems. That's usually something i enjoy but simply not up for it. I'll just get a new tablet to toy with true Android versions! My rooted Samsung SII with stock ICS is fairly easy to configure and navigate.
I'm in the same boat, tried to backup on my ext sd and now its stuck at generating md5. How do I stop or cancel this safely?
jreink01 said:
I'm in the same boat, tried to backup on my ext sd and now its stuck at generating md5. How do I stop or cancel this safely?
Click to expand...
Click to collapse
May need to force, power off
Sent from my XT907 using Tapatalk
sd_shadow said:
May need to force, power off
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Tried that, the only thing that worked was a battery pull. I thought I would ruin my ext sd but it looks like everything is ok. I just backed up successfully to internal. How come it hangs up on the generating md5 on the external sd but not on internal?
jreink01 said:
Tried that, the only thing that worked was a battery pull. I thought I would ruin my ext sd but it looks like everything is ok. I just backed up successfully to internal. How come it hangs up on the generating md5 on the external sd but not on internal?
Click to expand...
Click to collapse
Kindle Fire 1 doesn't have a removable SD card.
Sent from my XT907 using Tapatalk
sd_shadow said:
Kindle Fire 1 doesn't have a removable SD card.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
OK, thanks for trying to help.
---------- Post added at 10:15 PM ---------- Previous post was at 09:56 PM ----------
Update - I did a battery pull and it just seemed to reboot it. Nothing wrong with my external SD card that I can see. I can successfully do a backup on internal but everytime I try on external it gets stuck on generating md5. I have searched google but can't come up with anyone that has had the same issue on the g3. It's a sprint with model LG LG 990.Any help would be greatly appreciated. Just a thought, are there any other recoveries that work on my model g3?
jreink01 said:
OK, thanks for trying to help.
---------- Post added at 10:15 PM ---------- Previous post was at 09:56 PM ----------
Update - I did a battery pull and it just seemed to reboot it. Nothing wrong with my external SD card that I can see. I can successfully do a backup on internal but everytime I try on external it gets stuck on generating md5. I have searched google but can't come up with anyone that has had the same issue on the g3. It's a sprint with model LG LG 990.Any help would be greatly appreciated. Just a thought, are there any other recoveries that work on my model g3?
Click to expand...
Click to collapse
This is a thread for the Kindle Fire 1, you should be asking in a thread for your device, because the answer maybe be different
sd_shadow said:
This is a thread for the Kindle Fire 1, you should be asking in a thread for your device, because the answer maybe be different
Click to expand...
Click to collapse
Sorry, I typed in search g3 twrp freezing and this is what popped up.
I firstly tried to backup with TWRP on sd storage without luck, after 1,30h I give up and canceled that darn thing (the error says: "create tarfork process ended with error:255") and tried to backup on internal storage where it seems it work like a charm. Backup completed in 767sec.
Tweeks:
Camera Tweek (You need busybox installed for this), or you can unpack the zip and apply the patch manually/setting the permission corectly.
It will improve the overall video recording quality, by increasing the size limit cap of the video (old setting 600 Kb vs new 1200 Kb)
Custom Firmwares
Reserved
Recovery
CWM WITH ACCESS AT THE SYS_BOOT PARTITION ======>>>>> Bigger chance in bricking your device if you sleep while you flash something.
CWM NON TOUCH / NO ACCESS TO SYS_BOOT
Way to flash:
Version 1)
- enable usb debugging
- install adb drivers
- use the command adb reboot bootloader
- use the command fastboot flash recovery recovery.img
Version 2)
- shut down the phone
- press the volume key minus and power key
- use the command fastboot flash recovery recovery.img
Do not forget to unpack the zip files.
Please have in mind that with the no_sys CWM, you cannot restore the phone to stock using an official update.
Unbricking
Copied from here
Here's a small tutorial for people who bricked their phone while formatting the sys_boot partition in CWM Recovery. When you format that partition, nothing works except a screen shows up saying "RESET FOR ENTRY QPST DOWNLOAD". This screen is also known as the Qualcomm Diagnostic Mode.
Requirements:
A linux distribution (Ubuntu)
sys_boot.img (https://docs.google.com/file/d/0BxJJu-wXKdltTE90SGtEMmFQZHM/edit)
Follow the steps to restore the sys_boot partition:
1. Connect your phone to a pc using the cable
2. Install the drivers if necessary:
https://dl.dropboxusercontent.com/u/17562266/USB Modem Driver.rar
3. Open your terminal
4. Type "lsblk" (without the quotes).
You should see a list, showing every connected disk and partition. Look for a partition with a size around 50M. This is the partition we need, so remember the corresponding name under the 'NAME' column. It can be "sdc", "sdd" or "sde" followed by a number.
5. Cd to the directory you placed sys_boot.img in
cd [filename]
6. Type "sudo dd if=/dev/NAME of=sys_boot.img bs=512
Replace NAME with the name you got from lsblk, and press enter.
The output should look something like this:
3959420000 bytes (3866621 KB) copied, [ time spent], [KB/s]
7. Remove the cable from your device, do a battery pull and try to boot your device
Normally, it should boot correctly. If you formatted the /system partition too, you have to get into recovery mode by holding the upper volume button while booting, until a red screen appears.
If you have any questions, or if this doesn't work for you – let me know in the comments.
Thanks a lot to Adonis K. and globula_neagra for the sys_boot image and pointing me in the right direction.
Credits to DieterHolvoet from arctablet for putting it together.
THX! Much appreciated!
I own this device since today and you Sir made me very happy with your cwm and ability to root.
---------- Post added at 08:19 PM ---------- Previous post was at 07:42 PM ----------
I can confirm. Touchversion of CWM does not work.
File for non-touch CWM seems the same as touch btw. Could you please fix the link? Thx!
Yes, the touch version doesn't work.
The no-touch no-sys version works fine.
Here is the link for the no-touch/no-sys version (taken from the arctablet forums): http://globula.arctablet.com/ARCHOS_50_PLAT/CWM_A50_Plat_NoTouch_No_SYS.img.zip
globula must have misstyped it
IN CWM I cannot mount the sdcard. So I can't install any Zip-Files this way
Nash123 said:
IN CWM I cannot mount the sdcard. So I can't install any Zip-Files this way
Click to expand...
Click to collapse
I will fix these issues tomorrow.
Thank you!
GEN 11 ?
cajl said:
GEN 11 ?
Click to expand...
Click to collapse
Yes the Archos 50/53 Platinum and Archos 80 Xenon are Generation 11
NO !
it will be announced at IFA and I would see in Berlin
cajl said:
NO !
it will be announced at IFA and I would see in Berlin
Click to expand...
Click to collapse
I could try to convince you that they are Gen11, but you will have to trust me, the update page does not lie.
OK Archos 53 also ...
Anyone know if it's possible to partition the internal memory and internal sdcard together? I'm getting really low in internal space intended for app installations (180mb left, getting insufficient space errors)
Updated the third post with a new touch cwm, test version, i don`t have a platinum to test it.
Adonis, i don`t think is possible, tough you can use directory binder
I need some help with some file from the Archos 50 Platinum, I want to test if the phone function works on Archos 80 Xenon (it should in theory as this is not the first tablet made by Archos/Arnova that has a crippled phone function, my 7C G3 is capable if doing/receiving phone calls)
Hmmm, i see. In my previous phone the developers found a way to repartition the device and play around with them so we could balance the phone and internal memory to our advantage. Could really use the /storage/sdcard1 as part of my /data and /system partitions.
http://i.imgur.com/MJkdLS9.png
Never heard of directory binding, is it like symlinking?
I will test touch version in a few mins, gotta watch something first.
edit: Nope, touch still not working. Same results as the previous one.
Adonis K. said:
Hmmm, i see. In my previous phone the developers found a way to repartition the device and play around with them so we could balance the phone and internal memory to our advantage. Could really use the /storage/sdcard1 as part of my /data and /system partitions.
http://i.imgur.com/MJkdLS9.png
Never heard of directory binding, is it like symlinking?
I will test touch version in a few mins, gotta watch something first.
edit: Nope, touch still not working. Same results as the previous one.
Click to expand...
Click to collapse
Then it will be no touch for the moment, tough is strange, on the Archos 80 Xenon is working fine.
Not having the phone is a big impediment for me to test things, and I have the Xenon only till 28`th, so this is my main platform for testing for now (identical spec with the 50 Plat, even the partition layout is identical , that`s why i believe that the phone function should work)
I will do another try with the touch version from the Xenon in the next days, maybe with will work with that one.
Yes, the directory binding is the same as simlinking
Does anyone know a fix for the incompatability with older routers? (Non Wifi-N support).
Sorry for the OT btw.
Edit: Second question. How do I revert back to stock firmware or stock mode [without root and CWM-recovery]? I used the non_sys-version.
Edit2: Tomorrow I will flash original firmware. Hopefully the alterations will be gone.
Nash123 said:
Does anyone know a fix for the incompatability with older routers? (Non Wifi-N support).
Sorry for the OT btw.
Edit: Second question. How do I revert back to stock firmware or stock mode [without root and CWM-recovery]? I used the non_sys-version.
Edit2: Tomorrow I will flash original firmware. Hopefully the alterations will be gone.
Click to expand...
Click to collapse
I think you will need the sys_boot recovery for that, or the stock one, the non_sys boot will not allow you to flash stock firmware.
I understand it is currently not possible to unlock a Razr M with 98.18.94 or 98.30.1 OTA. Never the less, I had been trying to restore a previous VooDoo root that I deleted before the last OTA. Through the experimenting, I screwed up the flash on my phone, and recovering it, I found something that might be interesting.
As others pointed out, downgrading does not work. Flashboot gives various errors. When I screwed up my file system, I was able to flash from 98.18.94 (which I had) to 98.30.1 (which was the only download I could find) using RSD Lite. I was lucky it worked. And since I have been able to experiment and keep flashing 98.30.1 over and over.
I would like to report that in my experiments, I noticed an interesting fact about the recovery.img:
I am able to flash stock 98.18.78 recovery to my phone running 98.30.1.
I have verified the recovery.img contents are not the same, according to a WinMerge file compare, they are ~10% the same
When I try to flash twrp or cwm recovery, the only fastboot error is to the effect "wrong partition size".
The size of .78 and 98.30.1 recovery are the same, 10,485,760 bytes
On the other hand, if I try to flash the .78 system.img fastboot, or use RSD lite to flash .78, I see different security related errors on the phone's fastboot screen- none of which mention partition size. Of course, this is related to the Locked Bootloader I have.
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Right now my Razr M has gone from 98.18.94 to 98.30.1 with a 98.18.78 recovery. And I'm working ok.
I am not a professional Android Dev. But I am going to do the research and try to modify a cwm type recovery to match the size of a Moto recovery, and see what happens.
I invite anyone with real experience to contribute.
Bryan
bryanwieg said:
What did you say?
Click to expand...
Click to collapse
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.
aviwdoowks said:
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.
Click to expand...
Click to collapse
I have already found that if I take the OTA recovery and unpackbootimg and then mkbootimg without changing anything.. it recompiles down to aprox 5mb, which is different than the size it started from Moto.
So I am looking at if the size is set in how the img is compiled.
30.1 and .94 are the same updates, just different system versions. As for the other stuff, I'm not even sure what to say. I'm with Avi on this, I definitely would like to see what a dev has to say.
New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004
aviwdoowks said:
New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004
Click to expand...
Click to collapse
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.
bryanwieg said:
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.
Click to expand...
Click to collapse
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.
aviwdoowks said:
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.
Click to expand...
Click to collapse
Well, you'r right on the money. I appended data to a CWM recovery the same as Moto did to thiers, including the certificate at the end.
I didn't get a partition size error this time, but I did get a 'Failed to hab check for recovery'.
Granted, I didn't manage to place the 'empty data' at the same point in the file as the stock roms did. Other than that, it must be the certificate.
bryanwieg said:
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Click to expand...
Click to collapse
No, because it first checks the size (or whether it's a valid image at all) and if the size is correct, it checks the signature.
I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.
Really glad to see someone is still trying to find some sort of exploit for this device in it's updated state, it seemed like everyone had completely given up on it. My girlfriend recently grabbed a used Razr M to use for a while but it's fully updated, and I would love to be able to root it for her. I'll be following this thread to see if anything comes of this recovery downgrading
I'm pretty sure you can edit the props from what I can remember.
Sent from my XT907 using xda app-developers app
bryanwieg said:
I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.
Click to expand...
Click to collapse
You can use root eplorer free to extract the single img from the 404 or 411 xml.zips
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Here http://sbf.droid-developers.org/phone.php?device=8
---------- Post added at 10:48 AM ---------- Previous post was at 10:44 AM ----------
The razr hd (2), atrix hd, photon Q all use a recovery w/ same key. Git to work man!
Re:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.
815turbo said:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.
Click to expand...
Click to collapse
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.
I am willing to try it out. Win 7 64bit... pass me needed staf to flash it
Sent from my XT907 using xda app-developers app
please do
815turbo said:
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.
Click to expand...
Click to collapse
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".
benya274 said:
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".
Click to expand...
Click to collapse
I'll post it in just a few minutes. I will also post the required commands and we'll be backing up current recovery. If it fails, it should be no problem to restore your backed up recovery.
Download TWRP image on your phone from: titanroms.com/upload/rec.img
Please get to an adb prompt and run these commands:
su
cd /sdcard
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak2.img
Please ensure that both copies are 10MB. The dd command should end by saying "10485760 Bytes Copied" on all of the "dd" commands.
Now, you should have two backups of the recovery partition and the TWRP Image you downloaded from here all on your sdcard.
You can follow with these commands AFTER your backup has completed.
cp /sdcard/Download/rec.img /sdcard/rec.img
dd if=/sdcard/rec.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=twrprecbak.img
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
mv /system/recovery-from-boot.p /system/recovery-from-boot.bak
reboot recovery
In the event of a failed attempt at this you can run the following from adb:
su
cd /sdcard/
dd if=/sdcard/recbak1.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give me a holler if you don't understand this well. Good luck, guys.
I am gonna try it out tomorrow,i dont have time to do it tonight cause i need to go to work. My pc on work does not have internet connection I will keep u guys posted on any progress.
Sent from my XT907 using xda app-developers app
Just wanted to say I flashed the old ICS recovery to mine using fastboot commands but it didn't get me very far though.if I then try and flash the corresponding blur zip from recovery it just says invalid signature. Was trying to find a way to downgrade so I could get rooted..
Sent from my XT907 using Tapatalk
I can't enter recovery, only download mode. Using the send_command.exe tool, i am able to log in and dig around the file system. looks like my /dev filesystem is completely wiped out:
#df
Filesystem Size Used Free Blksize
/dev 1.37G 8.00K 1.37G 4096
/system 4.05G 3.14G 937.16M 4096
/cache 1.17G 2.04M 1.16G 4096
/data 22.73G 370.52M 22.37G 4096
/persist 27.48M 56.00K 27.43M 4096
#
notice that /dev is only 8.00K large (out of 1.37G). I have backups of all the partitions images on my hard drive and external SD card, trouble is i dont know how to restore those images as only download mode works. I have tried to re-flash a stock h811 KDZ using the LG Flash Tool 2014, which re-flashes fine, but still stick in bootloop. anyone have any ideas as to how i should proceed from where?
duuuuudeeeeeeeee
sidog said:
I can't enter recovery, only download mode. Using the send_command.exe tool, i am able to log in and dig around the file system. looks like my /dev filesystem is completely wiped out:
#df
Filesystem Size Used Free Blksize
/dev 1.37G 8.00K 1.37G 4096
/system 4.05G 3.14G 937.16M 4096
/cache 1.17G 2.04M 1.16G 4096
/data 22.73G 370.52M 22.37G 4096
/persist 27.48M 56.00K 27.43M 4096
#
notice that /dev is only 8.00K large (out of 1.37G). I have backups of all the partitions images on my hard drive and external SD card, trouble is i dont know how to restore those images as only download mode works. I have tried to re-flash a stock h811 KDZ using the LG Flash Tool 2014, which re-flashes fine, but still stick in bootloop. anyone have any ideas as to how i should proceed from where?
Click to expand...
Click to collapse
Did you factory reset after flashing the KDZ? Don't know if it makes any difference, was the KDZ the same version as was already on phone?
When I go to the factory reset option, my phone simply reboots - and foes back to its reboot loop. No recovery, all iI can do is enter simply enter download mode
What does it show up under device manager?
Sent from my LG-H811 using Tapatalk
device manager:
portable devices - LGE Android MTP Device
ports - LGE Mobile USB SErial Port
I'm thinking that if I can copy my .img backup files into the device, or mount the the external SD card while in the 'send_command.exe' interface, I can try to 'dd' restore eventually.
KDZ was the same as my phone (h811)
sidog said:
KDZ was the same as my phone (h811)
Click to expand...
Click to collapse
10a 10b 10c 10d? What version of the kdz for H811 did you have and which did you flash? Make sure they are the same.
H81110H_00.kdz - 10H, which is the same version as my phone.
sidog said:
H81110H_00.kdz - 10H, which is the same version as my phone.
Click to expand...
Click to collapse
Have you tried LG bridge on your PC? if it detects your phone, try to update it from there
yup, tried LG Bridge, it's just a light version of LG Support Tool...doesn't detect my phone...please note, I can only enter download mode
@sidog while your phone is bootlooping you can access adb and copy all your image backups back to your internal sdcard then dd them back to their various partitions
Sent from my LG-H815 using Tapatalk
i guess it depends on the nature of the boot loop culprit, but i myself cannot access adb at ANY time. ..... god does i've tried...is there something that i'm missing here?
did you find a solution to this? I'm kind of in the same boat...
nope, i'm still stuck...
Fix here:
http://forum.xda-developers.com/showthread.php?t=3107848
Sent from my LG-H811 using Tapatalk
that kdz flash method does NOT work for me. That was one of the first thing I tried. Flashed on multiple diff computers w/ no luck. As a last ditch effort, i even tried to flash the H810 model (HUGE MISTAKE). Now my phone won't even turn on
sidog said:
that kdz flash method does NOT work for me. That was one of the first thing I tried. Flashed on multiple diff computers w/ no luck. As a last ditch effort, i even tried to flash the H810 model (HUGE MISTAKE). Now my phone won't even turn on
Click to expand...
Click to collapse
Not good. Call LG for warranty replacement or your carrier.
it was a bad craigslist purchase on my part (bad imei after 2 months). Tried to salvage the situation but zero'ing on the imei but looks like I hard bricked it in the process. I'm just gonna but this brick in the closet until someone comes up w/ a solution (i kindda doubt it at this point, but you never know).
sidog said:
it was a bad craigslist purchase on my part (bad imei after 2 months). Tried to salvage the situation but zero'ing on the imei but looks like I hard bricked it in the process. I'm just gonna but this brick in the closet until someone comes up w/ a solution (i kindda doubt it at this point, but you never know).
Click to expand...
Click to collapse
Have u at least tried calling LG?
Sent from my LG-H811 using Tapatalk