All right you losers and screwups! Everyone who sucked hard at rooting has reason to rejoice!
Soft-bricking your phone may have been the best thing to happen to you.
Luck smiles on the unfortunate and the stupid today!​
Use a download manager to get these files, and check the MD5 of your downloaded file against AndroidFileHost.
Here's the latest rooted version from @diedemus
Here's the original rooted image for the H810PRa-310-410.
Know what you are doing before attempting to flash these files! Flashing the H810PR firmware is done mostly as a last resort for people who have bootlooping AT&T H810s.
Read all the instructions carefully, then follow the instructions in the root thread 1 through 6, except ignore the parts in step 4 where it mentions tar.gz and the filename since you have a rar file and already had to extract the image file from it and rename it to system.img.
You'll see that we have a different command to flash the H810PR compared to what was used on the H810. Here is the code to copy and paste at the # prompt in the command window:
Code:
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
Paste the above code in the command window, then hit enter and pucker your butt.
Wait for the # prompt to reappear.
Type LEAVE and hit enter.
Prepare to crap your pants again or savor the sweet taste of victory!
Good luck!
Feel free to ask questions, but try searching for an answer first please. XDA is loaded with information, but it's squirreled away deep in various threads. Learning to search XDA is a valuable skill. Even if you don't find an answer to your specific question, you'll learn something anyway.
H810PR is much better IMO than stock AT&T except for the danger of the green blob in the camera. There's hardly any bloat (like 100 less packages on the phone, seriously!), and no CarrierIQ to have to bother disabling. All the stuff AT&T broke is working too.
Cons so far:
Big ol' green dot in the camera. I wouldn't flash this rom unless I had to because of this issue.
No VoLte (voice over LTE). The phone drops to 3G in phone calls. Follow this post to enable LTE outside of a voice call.
Voicemail settings are grayed out. To set up, put your SIM in another phone or call ATT.
Editing options in camera are overwhelming! There's too many things you can change!
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 100 less.
The stuff AT&T removed or broke is not broke.
Editing options in camera are amazing! There's so many things you can change!
No CarrierIQ
Here's my H810 repository on Androidfilehost if you're looking for other H810 files.
This is pretty sweet! I always wanted to post in the dev folder, and make a reserve post. Not that I really did anything worthy of it, but I'm leaving the post here anyway.
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
It worked! It was a bumpy road, thank you for all your help! (oh sweet ad blockers, how I love you)
faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Yes to all your questions.
I repeated the code to flash here to make sure people noticed it was different for H810PR. It's the same in both posts.
Just noticed i no longer have volte with this image. (yes, i have lte)
faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
user787 said:
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
Click to expand...
Click to collapse
Copy OP's code @up..for me i follow till step 9 from THIS then follow this PAGE from 6 to 9 then paste OP code to flash image root
Please read carefully before anything bad happened
faizalotai said:
Please read carefully before anything bad happened
Click to expand...
Click to collapse
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
No problem bud
user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
I edited the OP to make the instructions more clear. Hope it helps!
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
noamaniac said:
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
Click to expand...
Click to collapse
Yes.
What is the LTE icon for this build? I have the 4G icon, but not sure this means LTE.
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
bobloadmire said:
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
Click to expand...
Click to collapse
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T (I don't know why I keep thinking this is possible, it isn't, bootloader is flashed by the KDZ and not compatible with the ATT versions anymore), but I'm going to stick it out on this image for awhile.
I'm keeping an updated list of the pros and cons in the OP.
phineous said:
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T, but I'm going to stick it out on this image for awhile.
Cons so far:
No VoLte (voice over LTE). The phone drops to 3G in phone calls.
Possible problems with voicemail.
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 150 less.
Click to expand...
Click to collapse
Would you Say the phone is snappier overall or is it mainly just to save storage?
bobloadmire said:
Would you Say the phone is snappier overall or is it mainly just to save storage?
Click to expand...
Click to collapse
I ran Debloater and blocked around 98 packages when I was on the AT&T H81010e non-root image. The phone was pretty fast, but something had a memory leak and I'd have to reboot it every morning. This image hasn't had that problem yet, but I've only been using it for a couple of days.
You might want to wait a little while for the people who had to use it to discover any more downsides. I think it'll be easy to switch back to an AT&T image, but I'm not 100% sure because I haven't tested it yet. (not possible till there's a TOT.)
In any case, I think it's a good idea to follow the instructions in the original root thread to extract an image of your working phone, name it something you'll remember, and keep it on the internal storage as an emergency recovery image.
Totes mah gotes. Thanks man.
Anyone that's on this Firmware having issues with voicemail? I can't seem to get google voice to work and when people call my regular voicemail it is saying i'm not available. I've tried entering the code into the dialer and i'm getting an error saying connection error or wrong MMI code.
I went into the forwarding settings in the phone and entered my GV # and received unexpected error from network.
Related
Hi there XDA community,
I would like to know if there is an up-to-day tutorial that has working file links? I would like to upgrade, root, and unlock my Xoom. I just bought a Motorola Xoom from 1saleaday.com the Model is an MZ601 and says "approved by IDA for use in Singapore" it is currently just as is and is not unlocked or rooted. I would like to get it upgraded, unlocked, and rooted so I can use it for what I got it for. It has WiFi and Data service that supports WCDMA 850/900/1900/2100, GSM 850/900/1800/1900, ATO_ITEM: AP1520AD3X3. It is currently running on Android Honeycomb 3.0.1, build number H.6.1-38-9. If you any ideas, files, links, tutorials (up-to-day), or can help, that would be great!
Thanks InfiniteImmortal.
P.S.
Here are the configurations;
Model Number: MZ601
Android version: 3.0.1
Firmware: GAS_ASIA_USAEVRSTURTIRD_P016
Baseband version: N_014.83.28P
Baseband configuration: UCAEVEUB1B8EU034.0R
Kernel: 2.6.36.3 [email protected] #1
Build Number: H.6.1-38-9
More specs will be provided if they are needs, thanks again II!
yeah, there are tons of tutorials, relatively up to date. Relatively, because the new method to root xyboards might work for classic xooms too. This method would not require you to unlock your xoom for rooting and thus allow titanium backup to backup all your data before unlocking and thus wiping your xoom.
Just from the first page in the Q/A- and Xoom-general forums:
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
Xoom root and bootloader unlock (a post by me)
and maybe this
[HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg
I order one from the same seller on E-bay today
and for sure need the same help
but I need some Q
is the seller ship the item quikly for you ?
is this come in sealed box ?
sorry but I'm afraid of them
Response to purity0flove
purity0flove said:
I order one from the same seller on E-bay today
and for sure need the same help
but I need some Q
is the seller ship the item quikly for you ?
is this come in sealed box ?
sorry but I'm afraid of them
Click to expand...
Click to collapse
It only took a week for me to get mine via UPS. The box came to my house sealed, it had never been opened. But I bought a new one, not a refurbished one. Hope this could help.
II
Response to llama-power
llama-power said:
yeah, there are tons of tutorials, relatively up to date. Relatively, because the new method to root xyboards might work for classic xooms too. This method would not require you to unlock your xoom for rooting and thus allow titanium backup to backup all your data before unlocking and thus wiping your xoom.
Just from the first page in the Q/A- and Xoom-general forums:
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
Xoom root and bootloader unlock (a post by me)
and maybe this
[HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg
Click to expand...
Click to collapse
Okay I will go and read these threads, but are you for sure they work on the EU models? I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore. This is one reason why I'm looking for an up-to-date threads that say they work with the EU models. If you could clarify more that would be great.
Thanks, II
InfiniteImmortal said:
It only took a week for me to get mine via UPS. The box came to my house sealed, it had never been opened. But I bought a new one, not a refurbished one. Hope this could help.
II
Click to expand...
Click to collapse
yes I ordered one from 1saleaday.com on E-bay .. this seller buy also on E-bay ... new not Refurbished ! and ship with UPS but didn't now still didn't ship and wait for him !
InfiniteImmortal said:
Okay I will go and read these threads, but are you for sure they work on the EU models?
Click to expand...
Click to collapse
Yes, the one post I have marked with "(a post by me)" is exactly how I rooted my xoom and that is a german MZ601. And it works, no brick
InfiniteImmortal said:
I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore.
Click to expand...
Click to collapse
That is weird. I have never read a thread about a brick that occured using the method I (and others) described. Could you maybe post a link to such a thread?
To Clarify this: the Unlock should impose absolutely no risk at all as it is a feature implemented by motorola. The recovery, even if it didn't work, wouldn't lead to a brick. And the universal xoom root should not do any magic either, it should only add two files to the filesystem (su and Superuser.apk) and remove those files that would make your new shiny recovery go byebye once booted
Ty my knowledge, only the "flashing a custom rom" part is a source of bricking. And that can easily be avoided by flashing a MZ601-rom instead of something else
That said, nobody can guarantee you that this is completely safe. There is a thread right next door with a poor guy whose xoom bricked itself overnight. That was a wifi-xoom, and so far no one knows why that happened. We're still working on a solution, though
InfiniteImmortal said:
Okay I will go and read these threads, but are you for sure they work on the EU models? I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore. This is one reason why I'm looking for an up-to-date threads that say they work with the EU models. If you could clarify more that would be great.
Thanks, II
Click to expand...
Click to collapse
tell me what way you chioce and made and the result .. cuz I will root my item when I recive
---------- Post added at 11:05 PM ---------- Previous post was at 10:54 PM ----------
If I root my xoom can I go back again on Original mood cuz I heard that if I rooted Xoom I will not be able to up-date it via OTA again !
purity0flove said:
If I root my xoom can I go back again on Original mood cuz I heard that if I rooted Xoom I will not be able to up-date it via OTA again !
Click to expand...
Click to collapse
yes, you will be able to go back to the original rom and lock your bootloader again. If you do that, you will be able to get ota updates (if you really want to do so, usually custom roms are ahead of the ota-updates)
You should make a backup of your xoom right after starting the new recovery, even before rooting. That will give you a set of files that, if you restore them, will reset your xoom back to stock, thus you'll only have to re-lock your bootloader to get ota-updates
Response to llama-power
llama-power said:
You should make a backup of your xoom right after starting the new recovery, even before rooting. That will give you a set of files that, if you restore them, will reset your xoom back to stock, thus you'll only have to re-lock your bootloader to get ota-updates
Click to expand...
Click to collapse
I'm now intrigued, I to would like to know how to do this. I'm all for safety measures when it comes to doing things that could damage my stuff.
II
Response to llama-power
llama-power said:
That is weird. I have never read a thread about a brick that occured using the method I (and others) described. Could you maybe post a link to such a thread?
Click to expand...
Click to collapse
Here are two of the links that I was telling you about
Motorola Xoom Root the Easy way
&
Xoom One-Click Root/Unroot
In the first one I found out about it in the comments sections. I read everything on the pages.
II
Custom ROM Files
Hey llama-power,
You say in your thread post that "If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file".
Do you by chance have the links to these files? I know I.C.S. is the latest one, but I'm happy with an old one if it is stable. Or if you have a custom ROM for the Xoom that would be great. I have a Samsung Captivate generation 1 that I use Firefly or Cognition on, along with the original stock ROM as backup just in case. Any links or files would be very cool!
II
Suggested Thread
Just to let you know your suggested thread "and maybe this [HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg" does not work on my Xoom, but thanks for your suggestion. I'll try the other ones you put up, so far I have read every page on every linked thread I've come across. Lots and lots of helpful info on those as well as your pages. But if you can respond to my three earlier posts that would be helpful too. Starting to get information overload, haha.
II
Response to llama-power
Just to let you know your instructions worked like a charm! Went step-by-step and everything worked with no problems at all.
A few more question, yes I know MORE questions! haha. Where is the backup I make stored at? I would like to put it in my backups folder for the Xoom under its drive in my computer. Currently the 3G data service is still not working on it, but is recognizing AT&T network. It says "Mobile Network State: Disconnected" just like before and suggestions? Other then that I also still don't have access to the micro SD card in Android, but can access it in the Recovery.
I now think its time for a new platform, NO more Honeycomb 3.0.1! If you have any suggestions your more than welcome to say or suggest just like for the other posts!
llama-power You ROCK!
Time for me to get some sleep! Been reading and doing Xoom stuff for hours now. I'll be on later to night to read your posts!
Sincerely, InfiniteImmortal
InfiniteImmortal said:
Here are two of the links that I was telling you about
Motorola Xoom Root the Easy way
&
Xoom One-Click Root/Unroot
Click to expand...
Click to collapse
Wow, wasn't aware of that. But these methods are really old. The method I mentioned is the universial root-method by solarnz which is supposed to work on every 'classic' xoom (despite the family edition with its locked bootloader)
InfiniteImmortal said:
You say in your thread post that "If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file".
Do you by chance have the links to these files?
Click to expand...
Click to collapse
I am using the team eos nightlies. Works really nicely except deep-sleep isn't working for me while wifi is enabled. Don't know if that is a rom-issue though, might be some app I use. Anyways, it's not really a problem to me, battery life is still more than sufficient.
You can get the team EOS nightlies for your xoom (MZ601 / umts_everest / EU-3G) from this thread. Download the latest nightly build and the latest G-Apps package (thats the Google Mail, Market, etc. apps) from the link in the same thread. Put those onto your sdcard and flash them from recovery. Wipe /data, /cache and dalvik-cache first, then install the rom, then the g-apps package and finally reboot. Do not reboot between the steps. When upgrading from one nightly to another omit wiping /data.
InfiniteImmortal said:
Just to let you know your suggested thread "and maybe this [HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg" does not work on my Xoom,
Click to expand...
Click to collapse
How did you determine that it didn't work? The only difference you should see is the new app "Superuser.apk". If it really didn't work: sad
InfiniteImmortal said:
Just to let you know your instructions worked like a charm! Went step-by-step and everything worked with no problems at all.
Click to expand...
Click to collapse
thanks, glad to read that
InfiniteImmortal said:
Where is the backup I make stored at?
Click to expand...
Click to collapse
on your sdcard: $SDCARD$/clockworkmod/backup/$DATE_AND_TIME_OF_YOUR_BACKUP$. just copy that entire folder, it contains many .img-files (one for each partition) plus another file for checksums. You will need all those files for a restore. You may, however, rename the directory.
InfiniteImmortal said:
I would like to put it in my backups folder for the Xoom under its drive in my computer.
Click to expand...
Click to collapse
great idea
InfiniteImmortal said:
Currently the 3G data service is still not working on it, but is recognizing AT&T network. It says "Mobile Network State: Disconnected" just like before and suggestions?
Click to expand...
Click to collapse
that is weird. What do you mean with "just like before"? As you haven't flashed another rom yet, nothing regarding connectivity should have changed so far. A few pointers to eliminate some errors: is Airplane mode off? Is mobile data enabled? Are you connected to a wifi-network? Did you set up your AT&T-apn correctly?
InfiniteImmortal said:
Other then that I also still don't have access to the micro SD card in Android, but can access it in the Recovery.
Click to expand...
Click to collapse
yeah, once you flash your new rom, you should be able to access that sd-card. As stated before, you are just rooted, that gives you the power to change things but if you didn't (like installing something that is supposed to give you access to your sdcard), nothing should have changed
InfiniteImmortal said:
I now think its time for a new platform, NO more Honeycomb 3.0.1! If you have any suggestions your more than welcome to say or suggest just like for the other posts!
Click to expand...
Click to collapse
see above, use team eos nightlies
Response to llama-power
llama-power said:
I am using the team eos nightlies.
You can get the team EOS nightlies for your xoom (MZ601 / umts_everest / EU-3G) from this thread. Download the latest nightly build and the latest G-Apps package (thats the Google Mail, Market, etc. apps) from the link in the same thread. Put those onto your sdcard and flash them from recovery. Wipe /data, /cache and dalvik-cache first, then install the rom, then the g-apps package and finally reboot. Do not reboot between the steps. When upgrading from one nightly to another omit wiping /data.
Click to expand...
Click to collapse
Okay I'll look into this one since I know you said it works for you.
llama-power said:
How did you determine that it didn't work? The only difference you should see is the new app "Superuser.apk". If it really didn't work: sad
Click to expand...
Click to collapse
I know you have already seen the other thread that I posted to, and about how I know it didn't work. You commented on the thread with your own post, thanks for backing me up.
llama-power said:
on your sdcard: $SDCARD$/clockworkmod/backup/$DATE_AND_TIME_OF_YOUR_BACKUP$. just copy that entire folder, it contains many .img-files (one for each partition) plus another file for checksums. You will need all those files for a restore. You may, however, rename the directory.
great idea
Click to expand...
Click to collapse
Thanks, I did the same thing on my Samsung Captivate and since my mother has the same phone I made it so it could be used on ether one, less file management for me. Haha
llama-power said:
What do you mean with "just like before"? As you haven't flashed another rom yet, nothing regarding connectivity should have changed so far.
Click to expand...
Click to collapse
You are correct on this, nothing has changed from before except becoming rooted and unlocked. I was hoping that just maybe a full system wipe might fix the connection issue I was having. I was being over optimistic!
llama-power said:
A few pointers to eliminate some errors: is Airplane mode off? Is mobile data enabled? Are you connected to a wifi-network? Did you set up your AT&T-apn correctly?
Click to expand...
Click to collapse
Yes airplane mode is off and Mobile data service is enabled. I have tried it with WiFi both on and off, before and after rooting and unlocking but still nothing. As for the AT&T-APN being setup correctly, I used the exact same settings that are being used in my phone with nothing different; but still to no prevail. Do you know if there is a settings list or configuration out somewhere for the APN?
llama-power said:
yeah, once you flash your new rom, you should be able to access that sd-card... if you didn't (like installing something that is supposed to give you access to your sdcard), nothing should have changed
Click to expand...
Click to collapse
Yeah I kinda guessed at that one, I remembered reading about the Honeycomb 3.1.0 update giving users the ability to use the micro SD cards today. That was before I read your post. lol You might know about this, Do you know where the repository of updates are located for the Motorola Xoom 'classic' model? I was thinking it would be a good idea to have all of them, if I ever wanted to use my warranty it would be good to have the latest stock ROM on it! It's better to be safe then up an icy creek in the Alps with a swim suit on!
II
InfiniteImmortal said:
Okay I'll look into this one since I know you said it works for you.
Do you know if there is a settings list or configuration out somewhere for the APN?
Click to expand...
Click to collapse
Just to let you know I'm using the ROM you recommended and I love it so far. As for the data service on the AT&T network it now works, after switching to the new ROM and it loaded the proper APN settings which were different from my phone. And of course with a new ROM the SD card now works as well. So my last and final question would be as stated before where can I find the oldest most up to date stock ROM?
Best regards, InternetImmortal
Sent from my MZ601 using XDA App on EOS
InfiniteImmortal said:
Just to let you know I'm using the ROM you recommended and I love it so far. As for the data service on the AT&T network it now works, after switching to the new ROM and it loaded the proper APN settings which were different from my phone. And of course with a new ROM the SD card now works as well.
Click to expand...
Click to collapse
glad you like it
InfiniteImmortal said:
So my last and final question would be as stated before where can I find the oldest most up to date stock ROM?
Click to expand...
Click to collapse
well, there are a couple of sources for a stock rom. For one, your sd-card should contain one (I restored my backup yesterday and yes, it even reset the recovery to stock)...
Also, motorola offers some filesystem images at http://developer.motorola.com/products/software/, but you'll need to register with them to get to the download (should be free, though)
Finally, it might be desirable to have some .sbf-file for your xoom. Those can be flashed using a software called rsd lite, even when you aren't able to enter your recovery system. Doesn't always work, so it's not more than a Hail Mary move... However, Motorola does a lot to keep these files from floating around the web, so I won't be able to provide you with a link.
As always thanks for the keen insight. Just came across a few threads that perked my interest. Have you ever tried to get working SMS text messaging and voice calling on the Xoom? Since I'm using the SIM from my phone to do the data I was hoping there might be a way. I haven't done a lot of reading on this yet but you seem to know everything.
Sent from my MZ601 using XDA App on EOS
InfiniteImmortal said:
Have you ever tried to get working SMS text messaging and voice calling on the Xoom?
Click to expand...
Click to collapse
nope. The sim inside my xoom is on the same contract as the sim in my phone and I had to pick one that would receive texts. Naturally, since I always carry my phone, that's where the texts go, so the xoom wouldn't ever receive a text ever anyways. Voice calling is currently not possible on the xoom. So the only upside of that would be that I could send texts using the xoom, but that isn't so much better than texting on my Desire HD. Plus, that would tear apart the messaging threads between my phone and the xoom.
However, there's a thread in the xoom development section where flashable zip-files are published for every eos nightly, you should be able to just flash that over your rom and thus enable texting.
Actually, I might try that some time, but right now I should really learn for that exam on friday:-/
SOLVED - How to flash the Proper (Fixed) Stock Rooted Image
Description: This is 100% stock with just Superuser/su added and overwrites every partition to stock but keeps your personal data, apps, settings the same (just like the stock factory image).
Samsung Official USB Drivers - Link
ODIN v3.07 - Link
Proper Rooted Stock Image - Download or (Torrent Link) - MD5 = be4350a56e739eaf7a4184352d653a7b
1. Install USB drivers
2. Download ODIN v3.07
3. Backup your data
4. OPTIONAL: Do a factory reset (highly recommended if you have issues with your current ROM)
***WARNING: Step #4 will erase internal storage but not microSD card***
5. Download the above Proper Rooted Stock Image file and extract the tar file from inside it
6. Boot phone into ODIN mode (See here for how-to)
7. Flash the extracted tar file using ODIN v3.07
You should now have a like new condition stock image and rooted with all issues resolved.
Credit goes completely to mrRobinson for creating this image for us. Thank you sir. (Original Post) + (Details How It Was Made)
To Install Official CWM Recovery
1. After following above process, download "Rom Manager" from the Play Store
2. Open Rom Manager
3. Select "Flash ClockworkMod Recovery"
4. Select "Samsung Galaxy S3 (Verizon)" down at the bottom and let it flash
5. Once completed you can reboot to CWM by selecting "Reboot into Recovery" from Rom Manager
ORIGINAL REQUEST
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
BungeBash said:
Just formatted back to stock until issues can be resolved. The stock image (which I'm told this root is + su) lost all Sprint instances and any strange extra options. Also the Keyboards are back to functioning. Not to be a conspiracy theorist, but I feel that the root image has more going on with it than what we are told.
Click to expand...
Click to collapse
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
If you don't like it, dont flash it.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Hardly helpful for those who already flashed it... I just want it fixed, or a work around. If it's something as simple as uninstalling a few things, or replacing some databases, I'm fine with that. I just don't want to redo everything, and re-restore everything with Titanium Backup.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
open1your1eyes0 said:
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
Click to expand...
Click to collapse
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
I did have some odd issues with SwiftKey crashing after flashing the image. Not sure if that has to do with it or not.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Useless post.
What would be useful is someone with the requisite knowledge being able to remake this exploit with the Verizon source in order to have maximum compatibility.
open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
alquimista said:
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
Click to expand...
Click to collapse
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
I could do it, but it'd require more time than whats it worth. Sorry.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
You are a WORM!!!!!!!
Sent from my Galaxy Nexus using xda app-developers app
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
Two completely pointless comments.
open1your1eyes0 said:
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
Click to expand...
Click to collapse
You sir are a better man than me for being so humble in response to these replies.
I'm assuming invisiblek DID in fact use the VZW image if the phone still had all the VZW nonsense in it (VZ Navigator, for example) as that would not be found in the Sprint image. Equally, if "all" he did was follow the steps in the link, then someone else doing the same is likely to produce the same result.
tonu42 said:
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
Click to expand...
Click to collapse
If you have these, have you posted them anywhere? That might have been a useful thing to do.
Here is all the removed apk's in a CWR zip.
http://www.mediafire.com/?6jv8wn9l5n0li9y
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
BungeBash said:
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
Click to expand...
Click to collapse
Thank you much sir. You assistance would be greatly appreciated.
Unfortunately I do not have a linux box so the guide does not work for me.
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Goose306 said:
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Click to expand...
Click to collapse
Considering I loaded the first root mod, then reverted to the image that it was created from and have 2 different setups I'd say two different files were used.
open1your1eyes0 said:
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
Click to expand...
Click to collapse
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
alquimista said:
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
Click to expand...
Click to collapse
According to users, flashing that sammy-update firmware got rid of all the issues and the Sprint related stuff. Just, FYI.
If anyone is up for the remake, you might want to try making it out of this one. Not sure if it's any different but it's from another well known Samsung firmware site.
Link to stock factory firmware
Good Afternoon,
I'm not sure what I did incorrectly but I am stuck at the screen with the Android belly open when trying to boot after using the Low Effort Method. I tried doing a factory restore and got nowhere with it. I do not see a stock KDZ for the ATT variant, what can I do at this point? Am I SOL until a dump is released for stock ATT or should I take my chances and bring it to ATT.
I'm assuming flashing the KDZ for any other variant would be a giant no no at this point.
(update) I see i'll need to wait for a TOT or take my chances with ATT, still anyone with a suggestion I appreciate it.
Any help is appreciated.
I am in the same boat, as of now there is no fix.
keeper22 said:
I am in the same boat, as of now there is no fix.
Click to expand...
Click to collapse
See the link below, i'll be trying in a little bit.
http://forum.xda-developers.com/g4/...are-to-stock-kdz-t3107848/page10#post62072832
EDIT: Confirmed WORKING. No issues so far.
Do you have root after your fix? (Thank you for the info and fix)
keeper22 said:
Do you have root after your fix? (Thank you for the info and fix)
Click to expand...
Click to collapse
No root yet, but I read the system.img was available to the developers. Possibly will see a file shortly.
Please post if you find any issues with your phone while using H810pr. So far I think I'm keeping it.
Just to let yall know that i've already submitted an image of PR to thecubed so we can get root
Mine bricked also. Not sure what went wrong. It went through the process like everything worked, the phone rebooted and that was it.
you can try the H810PR kdz to get you out of bootloop
phineous said:
Please post if you find any issues with your phone while using H810pr. So far I think I'm keeping it.
Click to expand...
Click to collapse
The only issues that I have had is not being able to get my LTE working. Other than that it seems to be running better than it was.
So just a heads up, I took a system image(PR version) and injected root but after flashing the image back I ended up with a bricked device (screen doesn't turn on, device recognized as Qualcomm HS-USB QDLoader 9008. I'm almost certain I didn't mess up in terms of the commands I entered when in send command mode. Anyways, I'm going to see if I can either fix this or get it replaced.
playgameo said:
So just a heads up, I took a system image(PR version) and injected root but after flashing the image back I ended up with a bricked device (screen doesn't turn on, device recognized as Qualcomm HS-USB QDLoader 9008. I'm almost certain I didn't mess up in terms of the commands I entered when in send command mode. Anyways, I'm going to see if I can either fix this or get it replaced.
Click to expand...
Click to collapse
Thanks for trying mate. I've been trying to find a Linux to do this myself. I guess there is more than to just follow the instruction of injection.
playgameo said:
So just a heads up, I took a system image(PR version) and injected root but after flashing the image back I ended up with a bricked device (screen doesn't turn on, device recognized as Qualcomm HS-USB QDLoader 9008. I'm almost certain I didn't mess up in terms of the commands I entered when in send command mode. Anyways, I'm going to see if I can either fix this or get it replaced.
Click to expand...
Click to collapse
Check the second post on the root thread. H810PR seems to be partitioned differently (see below). I'm glad they posted this and I checked the thread this morning because I was almost screwed again. The devs had said that the partition info was easy to view so we could figure it out for ourselves, but all the one click rooting has made me a lazy rooter.
H810PR
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
H810
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
Sorry for your loss!
Good news is that the warranty phone I got was a pristine H81010b. Hopefully you'll get the same. I made an image of it and now have dev upload on androidfilehost.com.
I'm posting unrooted images of H81010b, H81010e, and a hopefully properly extracted H810PR10a-310-410 now. If I have time today I'll give root injection another shot and upload the rooted files too.
phineous said:
Check the second post on the root thread. H810PR seems to be partitioned differently. I'm glad they posted this and I checked the thread this morning because I was almost screwed again.
H810PR
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
H810
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
Sorry for your loss!
Good news is that the warranty phone I got was a pristine H81010b. Hopefully you'll get the same. I made an image of it and now have dev upload on androidfilehost.com.
I'm posting unrooted images of H81010b, H81010e, and H810PR10a-310-410 now. If I have time today I'll give root injection another shot and upload the rooted files too.
Click to expand...
Click to collapse
I actually did see that and used the command they provided for getting the image and flashing it back. The inject script might have done something weird though because it failed at the umount command but i just ran that one command manually and figured everything would be okay but I guess it wasn't. I called ATT like 2 days ago before i flashed the PR kdz and they told me I can go to their device support store and that they would replace my device right there for me so hopefully that can still happen. I have an appointment at 5pm today
playgameo said:
I actually did see that and used the command they provided for getting the image and flashing it back. The inject script might have done something weird though because it failed at the umount command but i just ran that one command manually and figured everything would be okay but I guess it wasn't. I called ATT like 2 days ago before i flashed the PR kdz and they told me I can go to their device support store and that they would replace my device right there for me so hopefully that can still happen. I have an appointment at 5pm today
Click to expand...
Click to collapse
There's a new root injection thread here I'm going to try.
Let us know how it goes at with Device Support. I was told the one nearest me wouldn't have G4s yet.
Good luck!
Hopefully we can get these files tested by another sucker so you don't have to risk it!
playgameo said:
I actually did see that and used the command they provided for getting the image and flashing it back. The inject script might have done something weird though because it failed at the umount command but i just ran that one command manually and figured everything would be okay but I guess it wasn't. I called ATT like 2 days ago before i flashed the PR kdz and they told me I can go to their device support store and that they would replace my device right there for me so hopefully that can still happen. I have an appointment at 5pm today
Click to expand...
Click to collapse
I'm willing to test it out. I have a fully functioning h810pr and a backup phone in case my G4 toasted, it wont be a problem
bobimbap said:
Can you try this root injection instruction. It seem pretty well instructed. I dont have a Linux around to try
Click to expand...
Click to collapse
Well I don't have a working device right now to test on. I'm currently at work and need to stay on windows (all my IDEs are set up on windows). After work I'm going to head to the AT&T store to try and get my phone replaced. If no one was tried it by then I can. Also, it's not that hard to set up a bootable USB ubuntu drive (and is actually quite useful to have) so you could always do that.
playgameo said:
Well I don't have a working device right now to test on. I'm currently at work and need to stay on windows (all my IDEs are set up on windows). After work I'm going to head to the AT&T store to try and get my phone replaced. If no one was tried it by then I can. Also, it's not that hard to set up a bootable USB ubuntu drive (and is actually quite useful to have) so you could always do that.
Click to expand...
Click to collapse
I thought you can flash h810pr to unbrick your h810?
Well i dont have any knowledge in ubuntu either
bobimbap said:
I thought you can flash h810pr to unbrick your h810?
Well i dont have any knowledge in ubuntu either
Click to expand...
Click to collapse
No, I'm not stuck in the same mode I was before. I can't get into download mode. My screen stays black and I basically can't do anything (Which hopefully means ATT won't be able to see I had the PR firmware on there.)
playgameo said:
No, I'm not stuck in the same mode I was before. I can't get into download mode. My screen stays black and I basically can't do anything (Which hopefully means ATT won't be able to see I had the PR firmware on there.)
Click to expand...
Click to collapse
I've read through ubuntu pendrive instruction and root injection instruction. Looks like i might be able to do it. I will give it a shot when i get off work tonight.
bobimbap said:
I've read through ubuntu pendrive instruction and root injection instruction. Looks like i might be able to do it. I will give it a shot when i get off work tonight.
Click to expand...
Click to collapse
Good luck! Feel free to PM me if you need any help and I'll respond if I can.
Hello, those of you who have soft bricked and can still access download mode, there is a method a user and I @giantpear discovered to bring your phone back to life by flashing the KDZ of the Peurto Rican 810.
Instructions can be found at this thread:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Kudos to @hyelton for his original thread
Note: Remember you are flashing the Puerto Rican Firmware for your phone, not the original stock US KDZ as there is not one yet.
Note: I am not the creator of this thread I am merely re-posting what we found through test in that thread tonight.
Note: I am not sure moving forward if you were to continue to try to root or flash what model method you would want to try. I would say we should wait for a TOT method before trying anything else.
On the positive note, I now have a heavily debloated phone with zero ATT apps on it.
Hope this helps any who have lost their phone attempting root these past few days.
I approve But yeah it should be posted here in the mean time. Until we do get an official A&T TOT.
But this is great for either needing to go back to stock due to soft-brick, or if you like that pure software feeling.
Please make it known that this method isnt compatible for Low Effort Root AT&T H810 10g. I just tried and failed. Reflash the kdz and it all went well. I already submitted a system dump file to #thecubed. Hope we can get a rooted system img shortly.
Kudos @giantpear
user787 said:
Kudos @giantpear
Click to expand...
Click to collapse
@user787 Thank you! Your KDZ link saved at least a dozen ATT 810s. Power to XDA!
This is awesome news! I wish I would have found @user787 post earlier! Hopefully all the other lost H810 souls will see this post soon.
If anyone discovers downsides of using this KDZ, please post what you find in this thread. I've got a replacement phone coming and need to decide if I should keep this one or the AT&T phone. So far I'm liking this variant much better!
You guys should enter donation information in your profile. I'll buy you a beer or two!
would be awesome to make a combo rom with this and root for stateside AT&T phones. A factory heavy debloat rom would be nice since you are guaranteed that the removed apps won't cause issues.
phineous said:
I've got a replacement phone coming and need to decide if I should keep this one or the AT&T phone. So far I'm liking this variant much better!
Click to expand...
Click to collapse
I am with you, I think I will be sending back the warranty replacement they are sending me!
Although the process of bricking and pulling back (thanks to you guys) was a pain in the ass! I really like this ROM. I like it better than the one that came with my phone and so far I have no issues. When this version gets root I think it is the best case scenario. Thank you again for helping us all out!
Next I need to decide if I should take the updates available for it. I see there are ones available but none are being forced.
Edit never mind just app updates.
Sent from my LG-H810 using XDA Free mobile app
keeper22 said:
When this version gets root I think it is the best case scenario.
Click to expand...
Click to collapse
There's a root script out we can run on our system.img file, it just needs to be run on Linux. I'll try to set up a machine tonight if someone doesn't beat me to it.
phineous said:
There's a root script out we can run on our system.img file, it just needs to be run on Linux. I'll try to set up a machine tonight if someone doesn't beat me to it.
Click to expand...
Click to collapse
That's over my head, but I looking forward to it. Let me know if there is anything I can do to help.
Has anyone checked to see if they get good 4G LTE speeds with H810PR? I don't have good 4G coverage (or much data left) to test on. I just ran an LTE speedtest and I maxed out at 11.35 Mbps.
phineous said:
Has anyone checked to see if they get good 4G LTE speeds with H810PR? I don't have good 4G coverage (or much data left) to test on. I just ran an LTE speedtest and I maxed out at 11.35 Mbps.
Click to expand...
Click to collapse
Testing just now
noamaniac said:
Note: I am not sure moving forward if you were to continue to try to root or flash what model method you would want to try. I would say we should wait for a TOT method before trying anything else.
On the positive note, I now have a heavily debloated phone with zero ATT apps on it.
Hope this helps any who have lost their phone attempting root these past few days.
Click to expand...
Click to collapse
Another soul back from the dead.
Has anyone re-tried the Low Effort Root again?
informpage said:
Another soul back from the dead.
Has anyone re-tried the Low Effort Root again?
Click to expand...
Click to collapse
I tried and failed. However i already send a system img of PR to thecubed so we can get root
I've tried low effort root on my H810 last night and it worked perfectly. I've already installed a bunch of root apps and everything is working great.
---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------
bobimbap said:
I tried and failed. However i already send a system img of PR to thecubed so we can get root
Click to expand...
Click to collapse
It worked perfectly fine for me on my H810. At what point did it fail for you?
keeper22 said:
I am with you, I think I will be sending back the warranty replacement they are sending me!
Click to expand...
Click to collapse
I got the warranty replacement phone today. It's brand spanking new with H81010b firmware. I may pull an image off it later in case someone needs it, but I still think I'm sending the phone back. My original works too well to take a chance with new hardware.
probaina said:
It worked perfectly fine for me on my H810. At what point did it fail for you?
Click to expand...
Click to collapse
You probably used the 10g file on 10g system. I tried the 10g root file on PR system since my phone bricked earlier. I had to flash PR kdz to bring it back to life
bobimbap said:
You probably used the 10g file on 10g system. I tried the 10g root file on PR system since my phone bricked earlier. I had to flash PR kdz to bring it back to life
Click to expand...
Click to collapse
Oh I see. Ouch. Yeah I do have 10G system but I see what you're saying now.
phineous said:
My original works too well to now to take a chance with new hardware.
Click to expand...
Click to collapse
It might be because it was dead and now anything is better than that, but I feel like my phone is running better than before I tried to run Low Effort Root!
I haven't flashed either of these so I don't promise that they work. They ought to though.
I suggest you follow the instructions in the original root post under Commands to dump system.img and dump an image from your working phone. Name it something you'll remember and keep it on your internal storage. If something goes wrong from flashing the rooted image you can hopefully recover by changing the filename in the flash command to your original image. Don't run a factory reset or the original image will be deleted.
You'll want to rename the image file you extract from the RAR file. I named them with detail so I wouldn't get them confused.
Good luck!
A user reported that the H81010b image bootlooped their phone. Use at your own risk. You can flash the H810PR KDZ to recover but there's no going back to AT&T stock then. Keep a good copy of your original system.img on internal memory to recover and don't factory reset!
ATT_H81010b_Rooted.system.rar
ATT_H81010e_Rooted.system.rar
Why'd I use RAR? Why not? I'm one of those weirdos that paid for it. A site license even!
Here's my H810 repository on Androidfilehost if you're looking for other H810 files.
It says the img is not mountable, is it safe?
Edit: For 10e, yes it works.
thanks
and winrar 5 is awesome, love it. I've always been a fan of winrar
yoavst said:
It says the img is not mountable, is it safe?
Edit: For 10e, yes it works.
Click to expand...
Click to collapse
Here's a way to open the img file in Windows, but it's much easier to make an Ubuntu boot flash drive and mount it in Linux.
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Norcalz71 said:
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Yes I did with the original params for the G version (I had e).
Norcalz71 said:
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
@autoprime posted the commands to flash the different versions in the original root thread. All the AT&T H810 versions use the same command to flash.
The variables for the flash command are determined based on the location of the partition you want to overwrite in the partition table on the phone. There's a little discussion about it in the original root thread, but I'm sure it's discussed more in depth in rooting threads for earlier phones and threads about Android rooting in general.
phineous said:
@autoprime posted the commands to flash the different versions in the original root thread. All the AT&T H810 versions use the same command to flash.
The variables for the flash command are determined based on the location of the partition you want to overwrite in the partition table on the phone. There's a little discussion about it in the original root thread, but I'm sure it's discussed more in depth in rooting threads for earlier phones and threads about Android rooting in general.
Click to expand...
Click to collapse
Got it, thanks @phineous. I can follow directions like these pretty easily (it is all indeed low effort) but I like to try and understand the process behind the commands. So the seek/count/block size parameters, whether dumping a system.img or flashing a stock or rooted system.img are all the same for each command and for each software version across the H810? In this case they are:
bs=8192
seek=65536
count=579584
I'll have to dig a little more to learn how they figured out the proper parameters for each model.
Thanks again
Norcalz71 said:
Got it, thanks @phineous. I can follow directions like these pretty easily (it is all indeed low effort) but I like to try and understand the process behind the commands. So the seek/count/block size parameters, whether dumping a system.img or flashing a stock or rooted system.img are all the same for each command and for each software version across the H810? In this case they are:
bs=8192
seek=65536
count=579584
I'll have to dig a little more to learn how they figured out the proper parameters for each model.
Thanks again
Click to expand...
Click to collapse
It's the same for the AT&T H810s. The Claro H810pr that some us used after we killed our AT&T phones is different.
Look for posts about android partitions. @rightonred has a couple of posts where they show the partition table from our phones.
Here's the man(ual) page for dd where the commands (BS,SEEK,COUNT) are documented.
phineous said:
It's the same for the AT&T H810s. The Claro H810pr that some us used after we killed our AT&T phones is different.
Look for posts about android partitions. @rightonred has a couple of posts where they show the partition table from our phones.
Here's the man(ual) page for dd where the commands (BS,SEEK,COUNT) are documented.
Click to expand...
Click to collapse
Have a question for OP, this is just came into my head but flashing this img into 810pr fw will break the system itself as the seek and count partition are totally different..or what if we used code seek and count from PR??
faizalotai said:
Have a question for OP, this is just came into my head but flashing this img into 810pr fw will break the system itself as the seek and count partition are totally different..or what if we used code seek and count from PR??
Click to expand...
Click to collapse
That could work, but I don't know much about how the system checks itself and the bootloader. I think it would probably end up with the security error boot screen.
phineous said:
That could work, but I don't know much about how the system checks itself and the bootloader. I think it would probably end up with the security error boot screen.
Click to expand...
Click to collapse
autoprime said:
I just looked into the H810PR 10A files and it seems it's about equal to the AT&T H810 10G (newest ATT OTA). The H810PR 10A and the H810 10G (and I think 10E as well) have updated bootloaders with the "1" version... which was updated from the initial version out of box.. i think it was 10A (or 10b/10c/d.. not e/f).
So... obviously for people who were "bricked" (stuck in download mode) you should use this KDZ as that's about you're only hope at this point. KDZ will upgrade bootloader and you will be set at "1".. never to be at "0" again. 0 vs 1 doesnt mean anything yet... so it may not matter. But any possible bootloader exploit that may happen in the future that somehow only works on v0 bootloaders... you'll be out of luck. But lets hope that isn't the case. And who knows if there will even be an unofficial unlock.
For those who ARENT stuck in download mode but don't care about being on an updated "1" bootloader.. feel free to flash H810PR KDZ all you want.
For those who are on the original AT&T sw (10a/b/c/d) with a "0" bootloader who want root and wanna stay at "0"... someone with your 10a/b/c/d sw will need to dump and upload that system.img and then someone will have to root it.. then upload that img... then H810 10a/b/c/d users will have a safe root method that won't cause a security error and also won't update the bootloader. And maybe it'd be safe for now to keep the pre-rooted system.img (the one that doesnt yet exist as of the moment i am typing this) on your internal storage so if anything were to happen you could reflash system.. never needing an H810 KDZ/TOT (as long as you don't mess with other partitions).
Click to expand...
Click to collapse
@autoprime
I forgot about that post. It wouldn't work then. There was a version # in the build.prop that made me think H810PR had an older bootloader.
How do we determine/confirm if a software version bootloader count is at 0 or 1? I thought 10e was at 0 still but maybe not? Hopefully it is...
Sent from my LG-H810 using Tapatalk
Have we confirmed this works with 1010e? I just got the phone and that is the version installed and I want me some root
Edit, nvm it worked perfectly, thanks!
Rooted my at&t 10e with your image. Work great. Thanks.
Sent from my LG-H810 using Tapatalk
Obsolete
GvIn2it said:
Has anyone rooted their H81010b with this file?
---------- Post added at 09:01 AM ---------- Previous post was at 08:48 AM ----------
How can this work with the original root post, that file is 4GB. This one is only 1.6GB. Just interested to know. It's a little scary when someone posts:
"I haven't flashed either of these so I don't promise that they work. They ought to though." Where did they come from? Did you make them, or someone else who tested them? I would really like to try the H81010b but need a little verification.
Click to expand...
Click to collapse
You must extracted zip/rar to image..than copy to internal memory.
have you tried the H810 10b yet. I tried it on my phone and i keep getting a bootloop......
I really want my 4g back
scabbie1980 said:
have you tried the H810 10b yet. I tried it on my phone and i keep getting a bootloop......
I really want my 4g back
Click to expand...
Click to collapse
I don't think anyone has tested it yet.
Are you flashing it on an AT&T H810 with 10b or on the H810PR? It won't work on the H810PR.
If my 10b image really is broken I'll take it down.
Since none of the updates have prevented root, I doubt LG has made security changes to the bootloader. It's probably safe to upgrade to a new version. They're having a hard enough time making the phone work. I hope they're not wasting time patching, especially when we haven't even found a bootloader unlock. I could be wrong though.