Related
i flashed SCH-I500_USCC_DI14_REL.tar.md5。When I use odin Installation cmw ，the phone stopped at the samsung splash screen does not work. How can I do?
qq25 said:
i flashed SCH-I500_USCC_DI14_REL.tar.md5。When I use odin Installation cmw ，the phone stopped at the samsung splash screen does not work. How can I do?
Click to expand...
Click to collapse
You also need to flash the pit file. If you follow the instructions in this thread, it will tell you exactly what to do. You don't use Odin to install CWM, btw.
Phidelt82 is correct.
Start with that thread. That will get you back to stock.
Then this thread. How to Mod My MEZ. That will get you started from Stock to get Rooted and install CWM and then its your choice of ROM and Theme if you choose.
please please please.. read. read and read everything twice. go slow and have patience.
And ask questions. I do not get a chance to post so much at the moment but always willing to help where I can if I can.
now my phone can not to work。I press step by step, and now my phone finish except call 911, any other phone cannot dial, what reason be?
Need to activate？How should do?
qq25 said:
Need to activate？How should do?
Click to expand...
Click to collapse
Just cool down. Your phone is booting. It works. I don't work for USCC so I'm not exactly sure how it works but I don't know if you would have to activate it again. I suggest you take the phone to the store and tell them it stopped working. They will probably get it all fixed up for you there. Since it's stock right now you shouldn't have any problems (=
PS: In the future, don't dial 911 to 'test' whether you phone works or not.. 0_o
dcow90 said:
Just cool down. Your phone is booting. It works. I don't work for USCC so I'm not exactly sure how it works but I don't know if you would have to activate it again. I suggest you take the phone to the store and tell them it stopped working. They will probably get it all fixed up for you there. Since it's stock right now you shouldn't have any problems (=
PS: In the future, don't dial 911 to 'test' whether you phone works or not.. 0_o
Click to expand...
Click to collapse
thanks ,i use this phone in china ^_^ 。
qq25 said:
thanks ,i use this phone in china ^_^ 。
Click to expand...
Click to collapse
Why would you be using a US Cellular phone in China?
phidelt82 said:
You also need to flash the pit file. If you follow the instructions in this thread, it will tell you exactly what to do. You don't use Odin to install CWM, btw.
Click to expand...
Click to collapse
Woah, what do you mean you don't use Odin to install CWM? The newb guide
http://forum.xda-developers.com/showthread.php?t=931169
says "
1.Shut phone off, pull battery out and leave it out.
2.Run odin (assuming you have it installed)
3.Load the cwm-recovery-all.tar file into the PDA spot"
And i've read like 15 other how tos that all say the same thing. That sounds like you install CWM with odin.
I have seen a lot of unfinished info on UNROOTING so rather than see a bunch of people stuck like I was last night I thought I would toss a little guide together for everyone.
I take no credit for any guides I post just pitching in, if I help you CLICK me a THANKS!
download the asus firmware from here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
extract the blob from the zip file and put it in your adb folder located at something like:
AndroidSDK/platform-tools/
as you did to root the device.
open cmd promt window type the following and return after each.
\cd
\cd AndroidSDK\platform-tools\
adb devices
*adb your device make sure it is hooked up and id'ing your transformer.*
adb push blob /data/local
adb shell
*at the # type the following*
dd if=/data/local/blob of=/dev/block/mmcblk0p4
*wait a few mins to be safe*
now reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob” file. this will remove the clockwork recovery and put your tablet into BOOTLOOP this is ok.
----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Now that your tablet is stuck in a boot loop, put on the root of the micro sd card on your computer-> the update normally found in the asus/update/ folder from the firmware zip you download from asus. I used the .9 US update and it worked fine, you must then rename it to EP101_SDUPDATE.zip make sure you leave it a zip dont change the extension AND->make sure it is on the root of the card.
Now put your card in your transformer, hold the down volume and power till it prompts you in the upper left about wiping or booting to recovery**> let go and push up on the volume, which will load the factory recovery android with a box and a loading bar *** IF IT IS STILL CLOCKWORK RECOVERY THEN YOU MISSED SOMETHING START OVER DO NOT CONTINUE***> it will begin to flash the update do not bother it turn it off or anything else will take up to 10 mins to complete. it will restart and you will see the bar load again on boot up then it will boot to the asus logo and then to the homescreen and your good.
-Ian
Faved for later use when INeed to RMA
Sent from my Transformer TF101
I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.
Thanks for this. I have been holding off trying to root my Tablet until I had some clear indication that there would be a "way back".
I will PM you a link to V8.2.3.9 US Firmware as soon as it's done uploading to MegaUpload (Aborted as someone beat me to it)
I haven't found a need to root my TF yet as all I need for it is running pretty smoothly.
My phone on the other hand gets flashed with a new ROM every few days.
Great to know that I can go back if I do root one day. Thx
I get to this point...
ianandamy said:
...let go and push up on the volume, which will load the factory recovery android with a box and a loading bar...
Click to expand...
Click to collapse
See the box with a loading bar for about three seconds then the screen switches to the image of the android robot logo and an exclamation point within a triangle. I think its because I accidentally wiped my data last night when I was trying to fix the boot loop issue. I'm about to give up on this one...
Edit: Hey it works great, just make sure you don't add a .zip extension to the E101_SDUPDATE rename.
Big Thanks to ianandamy this works great! Got it up and running. The only problem is that I am being prompted to enter a password in order to get it to the homescreen...The second problem is that I never had a security password in order to access the tablet. I have a feeling this has to do with it being rooted by the previous owner before I purchased the tablet. Would the settings return to how he customized it pre-root? If so the password the tablet is asking for would be the one he set before I ever owned the tablet. How do I get around this?!
worked great, and like the profile pic
Added to ultimate thread. Nice job.
isdnmatt said:
I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.
Click to expand...
Click to collapse
Can someone host it and pm me a link to post
It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
isdnmatt said:
It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
Click to expand...
Click to collapse
GREAT!
I've extrapolated the WW version with that http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_WW_epad_user_8239.zip
This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
I'd do it, but I'm lame and don't have a linux box or VM setup .. that and I sold my eeePad to pay for vet bills... something about 'daddy save the puppy' is haunting me now.
P.S. Thanks for the info, just trying to save time if this is possible
sirmx said:
This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
Click to expand...
Click to collapse
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.
Segnaro said:
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.
Click to expand...
Click to collapse
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!
StirCwazy said:
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!
Click to expand...
Click to collapse
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.
Segnaro said:
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.
Click to expand...
Click to collapse
Sorry to be a bit pesky here, but just want to be real sure: Based on ROM work I've done on my Android phone, unrooting is not the same as going back to a stock ROM. Actually the reverse is true: you can apply a stock ROM< and it will effectively unroot the phone.
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?
ewingr said:
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?
Click to expand...
Click to collapse
Yes, and after a factory reset it would be like when you just took it out of the box.
Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147
b1ackplague said:
Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147
Click to expand...
Click to collapse
Yes, I went from 3.1 direct to .9 without any issue.
First poster here.
Hi I flashed a kernel from this link here
http://forum.xda-developers.com/archive/index.php/t-1513287.html
At first boot it had some of my apps, so I tried to reboot to get back the other apps, and it looked like a factory reset for my apps and home screen. So I did a nandroid restore for the backup I had right when I flashed the kernel. Now the screen is stuck at the boot, and it won't go into recovery. Any help please?
What kernel where you on before? If it was CWM 3.0 then 5.0 won't be able to restore.
How are you trying to get into recovery? What ROM?
Uhh I was on the stock kernel and gingerbread, i was on cwm 5 pretty sure, I got cwm from flashing that kernel
I'm trying to get into recovery by holding the volume buttons and the power button
How did you flash the kernel? It's a CWM flash which stock does not have. Did you heimdell it?
Not to interrupt hecheon - but follow the guide in the second link in my signature to restore your phone. And read it all for your benefit. Don't restore a backup. We can talk about that after you fix your phone.
lumin
No interruption here. Just trying to figure out what this guy did and how he did it. Could be a really simple fix. And I was gonna toss a coin to decide whether to link him your guide or juls.
Anytime time I read nandroid restore - better to start fresh. Link him to Juls' guide. He may find an easier read. I'm on the app.
hechoen said:
How did you flash the kernel? It's a CWM flash which stock does not have. Did you heimdell it?
Click to expand...
Click to collapse
I flashed it with sgs kernel flasher, I'm not home at the moment, I'll try the links asap
mtran1516 said:
I flashed it with sgs kernel flasher, I'm not home at the moment, I'll try the links asap
Click to expand...
Click to collapse
OK. Brainfart on my end. I forgot about that little tool. Follow lumins guide and you should be golden. Good luck.
lumin30 said:
Anytime time I read nandroid restore - better to start fresh. Link him to Juls' guide. He may find an easier read. I'm on the app.
Click to expand...
Click to collapse
Hey, I tried the second guide in your signature, I did everything right up to where I use Heimdall to flash. However, when I use Zadig to select my driver, and then flash, it prompts me to install my driver and open Zadig again. When I close it to try and just skip it, it just makes me wait, without any changes. I've been waiting for at least 30 minutes, how long am I supposed to wait for it to flash?
Let me know if you were able to get One-Click going. If not - try a fresh USB port that you have not plugged your phone in to yet if possible and start over.
lumin30 said:
Let me know if you were able to get One-Click going. If not - try a fresh USB port that you have not plugged your phone in to yet if possible and start over.
Click to expand...
Click to collapse
Nvm, I worked my way with Zadig, it worked
Thanks a lot man, and thanks to all the posters in this thread. You guys are great!
mtran1516 said:
Nvm, I worked my way with Zadig, it worked
Thanks a lot man, and thanks to all the posters in this thread. You guys are great!
Click to expand...
Click to collapse
What did you have to do? It might help other people that have a similar issue.
Shabbypenguin and the OUDHS
presents to you
OUDHS Touch CWM-based Recovery 1.0.3.3
for your AT&T Samsung Galaxy Express
Read this whole post before doing anything
Enjoy
Odin Flashable - OUDHS CWM-based Recovery 1.0.3.3
Odin 3.04
Drivers
Directions:
1) Download the above files
2) Extract Odin3-3.04.zip and copy the tar that you downloaded into the folder
3) Run Odin as an administrator
4) Power your device off
5) Press and hold volume down and power to enter download mode
6a) Connect your phone to your computer
6b) Wait for drivers to finish installing if they need to be
7) You should see Odin find your device by marking a blue square in the ID COM box
8) Click on PDA and choose the recovery tar you downloaded
9) Click start
-----------------------------------------------------------------------------------------------------------------
Congrats you now have CWM now if you wish to root youll need to follow these instructions
-----------------------------------------------------------------------------------------------------------------
SuperSU+ 1.25
Directions:
1) Download the above file
2) Connect your phone and copy them to your phone
3) Once they are copied power down your device
4) Hold volume up and power to enter Clockworkmod recovery
5) Navigate recovery by using the volume keys and power to select
6) Choose install zip from sdcard, then pick internal or external (where you copied it to)
7) Scroll down to the SuperSU+.zip and select it to install
-----------------------------------------------------------------------------------------------------------------
Congrats you are rooted! this procedure will work on any firmware update you guys get
-----------------------------------------------------------------------------------------------------------------
If you enjoyed getting root/recovery and want to show appreciation you can always buy me a coke
Source
Credits:
Members of the Official Unloved Devices Hit Squad (OUDHS) For being the best we can for those whom need us
rdawson28 For being an awesome tester
BlindArtisan For providing the stock recovery, thanks man
I can't use the cwm because no matter what I try I can't get my goddamn phone to be recognized properly in download mode. It's seen perfectly when powered up on com3. When I go into download mode it's listed as an unspecified device and the usb modem driver doesn't turn on for the phone like it does when it's on.
Thank you for doing this it has been long overdue. Do you think you could provide the recovery image (and other files needed for installation?) without having to use the exe?
BlindArtisan said:
Thank you for doing this it has been long overdue. Do you think you could provide the recovery image (and other files needed for installation?) without having to use the exe?
Click to expand...
Click to collapse
www.shabbypenguin.com/OUDstuff/Samsung/ATT/Express/Express-OUDHS-CWM.tar
Thank you. An alternate way to install for those who are rooted and don't want to use Odin.
Create a copy of the recovery on your sdcard.
In the android terminal or adb with shell type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
To make the recovery permanent.
Find /system/etc/install-recovery.sh
Rename the file install-recovery.sh.backup
Reboot into recovery and enjoy the glory.
Sent from my rooted SAMSUNG-SGH-I437 using xda app-developers app
JDC2389 said:
I can't use the cwm because no matter what I try I can't get my goddamn phone to be recognized properly in download mode. It's seen perfectly when powered up on com3. When I go into download mode it's listed as an unspecified device and the usb modem driver doesn't turn on for the phone like it does when it's on.
Click to expand...
Click to collapse
I had the same issue, and I narrowed it down to this: If you installed the samsung usb driver WINDOWS UPDATE then you are screwed. What you really need is a laptop with no phone drivers on it, and just plug your phone while it's on download mode and then it will be seen by ODIN. I had to use another laptop to install the recovery correctly.
Sworder said:
I had the same issue, and I narrowed it down to this: If you installed the samsung usb driver WINDOWS UPDATE then you are screwed. What you really need is a laptop with no phone drivers on it, and just plug your phone while it's on download mode and then it will be seen by ODIN. I had to use another laptop to install the recovery correctly.
Click to expand...
Click to collapse
You could always uninstall the drivers then install fresh ones from Samsung. Or use the in phone method.
Sent from my rooted SAMSUNG-SGH-I437
I has to uninstall then put the fresh drivers on thats the easiest way
Sent from my SAMSUNG-SGH-I437 using xda app-developers app
Anyone else's recovery think it's march 13, 1970?
Also, I'm curiuos as to why it tries to fix root when I reboot and what, exactly, would it do to fix it. After reboot, root is not broken, so a fix is apparently not needed.
invert_nexus said:
Anyone else's recovery think it's march 13, 1970?
Also, I'm curiuos as to why it tries to fix root when I reboot and what, exactly, would it do to fix it. After reboot, root is not broken, so a fix is apparently not needed.
Click to expand...
Click to collapse
I have the exact same issue with the date.
I don't quite understand what you are saying, but It doesn't try to fix root on boot it tries to fix the recovery.img
Sent from my rooted SAMSUNG-SGH-I437
Thanks blind you came through for me, that way I didn't have to worry about my phone being recognized in download mode. Nice job on the recovery it looks fantastic.
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Someone needs to make a video about this root method to spread the word and upload it to youtube!
Worked flawlessly on a new phone. A 6 month old one, all appears ok, it sees the phone, odin loads the image, phone reboots ok. When I try try to reboot into recovery mode I get the stock recovery, not CWM.
Any ideas?
guys i am so sorry, i had to reinstall linux and thought i lost teh device t ree, anyways i compiled a new version of OUDHS recovery for yall. and finally uploaded source
Carpboy,
Did you delete/rename install-recovery.sh as referenced earlier in thus thread?
Shabby,
Thanks a lot. What changes are there in this new version? Also are you still planning on making the source public?
invert_nexus said:
Carpboy,
Did you delete/rename install-recovery.sh as referenced earlier in thus thread?
Shabby,
Thanks a lot. What changes are there in this new version? Also are you still planning on making the source public?
Click to expand...
Click to collapse
source is at the link
and there is a good deal different in the latest version. honestly i suggest everyone upgrades
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
invert_nexus said:
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
Click to expand...
Click to collapse
Havent updated yet but sounds like the same problem as before ill test tomorrow been really busy also gonna work on the cooked up rom more when I get a chance im sure the recovery issues will be fixed shortly
Sent from my SAMSUNG-SGH-I437 using xda app-developers app
invert_nexus said:
Just tried it.
Two things:
1.) The colors are off. I'm guessing it's identical to the issue rdawson detailed in the earlier debugging process. Also, the display jumps from side to side with each display change. I.e. each scroll up or down in a menu, also when the backup moves from file to file.
2.) The date of the backed up file is still 1970. Although, oddly, the properties of the files are dated 1979.
Click to expand...
Click to collapse
the time will always be off, recovery doesnt talk to the rest of the phone. crap, did that get fixed? or was it always broken?
shabbypenguin said:
the time will always be off, recovery doesnt talk to the rest of the phone.
Click to expand...
Click to collapse
Odd. Is that just an ussue with this phone?
crap, did that get fixed? or was it always broken?
Click to expand...
Click to collapse
You're talking about the display corruption?
Your previous version worked fine. Something must have reverted.
invert_nexus said:
Odd. Is that just an ussue with this phone?
You're talking about the display corruption?
Your previous version worked fine. Something must have reverted.
Click to expand...
Click to collapse
the time this is android wide afaik. twrp and official cwm have teh same bug :/
and crap that means some of the new features broke stuff for yall :/ ill put the old on back up in the OP i was really hoping to give you guys touch recovery
I used Sunshine, got root and S-Off, flashed a wireless tether zip. Right after, 4G speeds plummeted and no websites would load. Saw the closest to going back was to RUU, couldn't get it to open the file (even in the SDK folder after I downloaded and installed all files). Finally flashed another ROM and wiped everything from my phone.
Still 99% of webpages won't load on 4G. If they do, it takes forever. Not sure if it's anything I did, but just wanted to ask before it turns out to be some huge coincidence with Verizon. Thanks for any help.
Yazzinit said:
I used Sunshine, got root and S-Off, flashed a wireless tether zip.
Click to expand...
Click to collapse
Which one?
Right after, 4G speeds plummeted and no websites would load.
Click to expand...
Click to collapse
Pretty good indicator for what's wrong?
Saw the closest to going back was to RUU, couldn't get it to open the file (even in the SDK folder after I downloaded and installed all files).
Click to expand...
Click to collapse
You have fastboot drivers installed on your PC?
Finally flashed another ROM and wiped everything from my phone.
Click to expand...
Click to collapse
Which one?
Still 99% of webpages won't load on 4G. If they do, it takes forever. Not sure if it's anything I did, but just wanted to ask before it turns out to be some huge coincidence with Verizon. Thanks for any help.
Click to expand...
Click to collapse
Flash CleanROM. It's just like stock only better: debloated and tweaked, tethering enabled and more...
Thanks for the reply.
The wireless tether zip I flashed was: http://forum.xda-developers.com/showthread.php?t=2708548
The ROM I'm currently on is: http://forum.xda-developers.com/showthread.php?t=2716306
- Nothing wrong with it, just don't like the stock look and loading webpages is still not working.
I have fastboot drivers and adb as well as the SDK toolbox on my PC. I've been able to do most things following guides and posts here, but I can't RUU. When I flashboot flash zip 0P6BIMG.zip it gives error: cannot open 0P6BIMG.zip. I guess I could buy an external SD card and reader, but was hoping to fix this tonight/tomorrow.
Trying to download CleanROM for the 5th time tonight. The download stops around 300-400MB and there's no other mirrors for it. Currently at 700MB, maybe this download will go through (on PC). I'm really just trying to fix my webpage issue and go back to stock (or CleanROM is fine if it's similar). I'm willing to even donate a little to someone.
Yazzinit said:
Thanks for the reply.
The wireless tether zip I flashed was: http://forum.xda-developers.com/showthread.php?t=2708548
The ROM I'm currently on is: http://forum.xda-developers.com/showthread.php?t=2716306
- Nothing wrong with it, just don't like the stock look and loading webpages is still not working.
I have fastboot drivers and adb as well as the SDK toolbox on my PC. I've been able to do most things following guides and posts here, but I can't RUU. When I flashboot flash zip 0P6BIMG.zip it gives error: cannot open 0P6BIMG.zip. I guess I could buy an external SD card and reader, but was hoping to fix this tonight/tomorrow.
Trying to download CleanROM for the 5th time tonight. The download stops around 300-400MB and there's no other mirrors for it. Currently at 700MB, maybe this download will go through (on PC). I'm really just trying to fix my webpage issue and go back to stock (or CleanROM is fine if it's similar). I'm willing to even donate a little to someone.
Click to expand...
Click to collapse
Scott's site is not mobile friendly, but he just put up a DevHost mirror:
http://forum.xda-developers.com/showthread.php?p=55135177
The download actually finished, I even checked the MD5 of my download vs. on his site, matched. Wiped and flashed it, got dialer.apk stopped working, hit ok, popped up again, hit ok, phone bootlooped with 3 colored android lights on screen. Rebooted manually, same error, then something like phone.apk or android.google.something stopped working, hit ok, boot loop again. Pretty much have no clue at this point.
Yazzinit said:
The download actually finished, I even checked the MD5 of my download vs. on his site, matched. Wiped and flashed it, got dialer.apk stopped working, hit ok, popped up again, hit ok, phone bootlooped with 3 colored android lights on screen. Rebooted manually, same error, then something like phone.apk or android.google.something stopped working, hit ok, boot loop again. Pretty much have no clue at this point.
Click to expand...
Click to collapse
That sounds as if you dirty flashed CleanROM over the GPE.
Did you wipe cache, Dalvik and data before flashing CleanROM?
If not, do it and reflash the rom.
I may have messed it up, it was late last night. I have TWRP on it after following guides since I somehow lost the OS while trying to RUU different ways. Can anyone confirm everything I need to wipe so that I can flash CleanRom without wiping it from my internal storage? Don't have an external SD card and it won't sideload for some reason (I get error: cannot open romname.zip).
Edit: That worked. Except now it says CleanROM 1.3 in my settings lol and I swear I downloaded 1.4, since it was from the developer's site directly.
You do not need to flash a tether zip on that ROM or any other custom ROM
Sent from my HTC One VZW using Tapatalk 4
You're right. At the time I just wanted to add tethering and not change anything or flash any ROMs. Beyond that point now lol. CleanROM looks fine and is working well, it just says 1.3 in settings when I know I downloaded 1.4 from the OP's site last night.
Yazzinit said:
You're right. At the time I just wanted to add tethering and not change anything or flash any ROMs. Beyond that point now lol. CleanROM looks fine and is working well, it just says 1.3 in settings when I know I downloaded 1.4 from the OP's site last night.
Click to expand...
Click to collapse
It's a typo. ?
Scrosler provided a zip to change the version number. I believe it's in post 2
berndblb said:
It's a typo. ?
Scrosler provided a zip to change the version number. I believe it's in post 2
Click to expand...
Click to collapse
You are correct and thank you for the kind reply, unlike another in that topic who took the same amount of time to be rude for no reason. Thanks to all for their help, looking good now and working good, and extra features to boot.