my eyes are bleeding here from reading and i have a couple questions, easy it think.
i'm rooted, via z4. i (think) i installed clockwork properly but when i go to enter recovery (power and volume+ on boot) it says "revovery something has been pressed" or something and then i see a quick triangle with an exclamation before it boots normally.
does that mean i have installed clockwork properly and it just doesn't have an image to boot from?
if so, how do i make a stock image before i flash a new rom?
additionally, i'm pretty sure i got a previously returned tablet sold as new. can anyone confirm that their unit came with the plastic screen protector, the ones you peel off before using?
so, if i do a factory reset, does that wipe any ecidence of mucking around with root or do i need the stock image reflashed?
thanks for your help!
If you see the exclamation point, then you don't have clockworkmod - you still have standard recovery.
I have an update.zip for clockworkmod .8 in my TnT Lite post, here in the dev section. I would recommend that version as it works with all the mods here, as well as stock ROMS. If it works, you'll see recovery come up with the the power vol up combo.
I think new tabs did not come with the screen protector. Mine did not, but it came with a green microfiber cloth instead of black
Correct, only the first batch had a screen protector.
Other than the obvious things like fingerprints on the screen or the plug being completely assembled in the box, one other tell-tale sign is whether the plastic wrapping around the box is missing. I remember the plastic wrapping because I was concerned with my first purchase and the 15% restocking fee, so I knew that the plastic was a way that they could tell that the box was opened. But, you can use the same thing to check on your end.
If you need to return it and want to wipe it clean, I would recommend running the latest stock ROM (which wipes recovery as well) and then do a factory restore after it reboots. It will actually reboot into their EULA, so it really looks like its completely wiped clean.
ahh, well i'll do the clockwork again.
as for the new/restocked unit, the screen protector was the icing really. it came with a yellow (to my eyes) wipe but the kicker is the EULA, set up wizard wasn't what greeted me on boot. it had been half set up and was crashing when i tried to change display settings or open email app.
i think i'll tell them i'll keep the tablet if they give me the 3 year accidental for free and see what they say. it works great after factory reset and updates. and the screen is fine and all...
actually, my buddy just noticed a stuck pixel- it shows red on black but can't be seen on differnt colors.
SO, if clockwork didn't install correctly, only z4root, will a factory reset be enough iif i bring it back?
edit---- figured it out
ok, so i swapped out the first unit and got a price match to boot but when i boot this new unit for the first time, same as the first- no setup wizard/EULA agreement that you see on a fctory reset.
wth. these are both from staples.
The EULA only shows up with newer devices - it wasn't in the original firmware.
You can verify by updating the firmware and then wiping the user data. The EULA will pop up when you reboot it. Not having is actually a GOOD thing because it means its probably an unused device - I would be wary if my device came with an updated firmware as it could be a refurb that they are selling as new.
Related
I've got cyanogen's optimized 1.5r2v3.4, and Recovery Image v1.2. I have read half a dozen threads on how to get your phone back to stock, including this one http://forum.xda-developers.com/showthread.php?t=491350, but I have a unique impediment.
The screen on my fiance's brand new phone completely stopped working after less than a week. I can only interact with the phone via adb connected to the recovery shell, so I have to be absolutely sure it goes perfectly the first time (since the odds of having a working recovery shell after a bad flash are slim). I have not changed the second splash screen, so by what I read, all I need to flash back are the SPL, then the DREAIMG.nbh, correct?
How do I do update.zip for flashing the SPL via the recovery console? I had no problems getting the phone from stock to rooted, followed the instructions step by step. But now that I have to try and figure out how to do EVERYTHING via adb ONLY, I read the most simple instructions and find myself going 'wait, what?', trying to figure out how that would work done entirely without being able to see feedback on the phone screen.
Use the DREAIMG.nbh and recovery.img for rc29 stock its in the rooting thread.......load up the phone in fastboot (camera and power button) the phone will recognize the files and tell u to hit a button....you hit that whopping one button and wait 2 minutes and you'll be back to stock rc29 where then you can reroot or just sit around waiting for Over the air updates from t-mobile to catch u up to cupcake.....honestly i don't use fastboot EVER but i always keep those two files on my sdcard so if i have a problem i just run it and blast back to rc29 and start over......hope u see this before its closed in 5 seconds for not using the SEARCH BUTTON
sorry just use just reread ur post...use the DREAIMG.nbh it has the old SPL built into it
i'm not sure how this would be done, but what iwould suggest is put the original SPL on the SD card as update.zip and the DREAIMG.nbh on the sd in the root of the sdcard, then reboot holding home, give teh phone 5 minutes to boot into recovery then press alt+S wait 10 or more minutes to let it flash and then press home and back to reboot, or in adb shell type reboot bootloader, give it a minute or so and then press power, wait 30 minutes and hit the trackball, if after hitting the trackball the phone vibrates then it went fine, if not then the .nbh didn't flash
tubaking182 said:
i'm not sure how this would be done, but what i would suggest is...
Click to expand...
Click to collapse
Yeah, that sounds like a plan. Thanks, I just really couldn't get my head around how I could possibly do this!
Can I ask why you are bothering? Are you afraid they will hit you with an out-of-warranty fee because it's rooted? They won't, I've returned a first gen G1 that had the issue of the screens ribbon cable coming unplugged (sounds like your problem) and T-Mobile sent us a new one no problem.
GenericNode said:
Are you afraid they will hit you with an out-of-warranty fee because it's rooted?
Click to expand...
Click to collapse
Yeah, actually. *shrug* it doesn't seem to have flashed back to the stock image anyway, so I guess it'll have to go back in whatever form it's in. Hopefully you're right and they don't care about custom images.
heldc said:
Hopefully you're right and they don't care about custom images.
Click to expand...
Click to collapse
They sure didn't care about mine.
And besides, whether or not your phone is rooted isn't in the check-list of questions a CSR is supposed to ask before accepting a return, so how could it be your fault?
Actually they asked me repeatedly if i botched rooting my phone, i kept asking what that meant and they moved on after the third or fourth time they asked(which i found odd since the demo phone in my t-mo store is rooted and running dude 1.2). as long as it doesn't have a custom splash screen it should be ok.
also you could always grap the OTA update and edit it in some way(resize a pic and put it back) and then resign with testkeys and rename update.zip then the only thing they'll see if they really look at the phone is a bootloader that's been changed and recovery, but the rest will look like their stuff.
tethering caused double post sorry
tubaking182 said:
Actually they asked me repeatedly if i botched rooting my phone, i kept asking what that meant and they moved on after the third or fourth time they asked
Click to expand...
Click to collapse
No way. Sweet. I haven't seen this policy yet, but I never pay attention
yeah well, i have had enough experience rooting and un-rooting to the point that i decided that when my replacement arrived i rooted it with my eyes closed, i had all the needed files on my sd card and comp so i used adb install and memorized the steps. only took an hour to do. the thing i hate when i am on the phone with them is when they ask me to reboot/pull battery/wipe when i tell them i tried all that and then i called.
tubaking182 said:
yeah well, i have had enough experience rooting and un-rooting to the point that i decided that when my replacement arrived i rooted it with my eyes closed, i had all the needed files on my sd card and comp so i used adb install and memorized the steps. only took an hour to do. the thing i hate when i am on the phone with them is when they ask me to reboot/pull battery/wipe when i tell them i tried all that and then i called.
Click to expand...
Click to collapse
When you talk to those people you have to sound as newbish as possible, that's probably why they kept asking if you rooted it.
trust me i sound like a freaking idiot. "they told me on the t-mobile forums to press the homekey and turn the phone on and i got a triangle with an exclamatioin point, and then i pressed alt+w and after a few seconds my phone rebooted but the screen is always sideways when i open apps." i act like an idiot and they replace it. the only problem i had was when the guy asked what my favorite thing about the phone is, right after i told him i didn't know what root was. i just said games cause that's all i could come up with
Alright, so last night I was fooling around with "Type Fresh," which you guys have probably heard of. It was released here... It's a font changer...
Anyway, things were going good until I tried a font named, "Joystix," which replaced quite a few of my fonts. That caused my phone to go into a crazy bootloop.
So, at this point, I do not have Clockwork Recovery. I actually have the Stock Recovery. For some strange reason, my stock recovery just takes me to a screen with a red triangle, and factory reset just shows this hard drive and a loading bar that never goes anywhere before rebooting my phone into a boot loop.
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
wauterboi said:
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
Click to expand...
Click to collapse
Well I've never personally used type fresh to change fonts, I've done it in other ways. Just a thought for ya, but I would recommend that if you can get adb to recognize your device (cmd: adb devices) try booting into hboot(volume down + power), and see if it recognizes it regularly that way, from there I recommend trying a program called Droid. It's a windows program that I used when I messed up re-rooting my replacement mt4g (tip: Don't try rooting when having been awake for 26 hours for no apparent reason ). It has a feature called Debug Console which fixed a bootloop, and constant force close that I somehow managed. I also suggest pulling your sdcard, getting a usb scard reader, and installing the stock recovery zip (Pdimg or something like that, I forget off hand).
That's all I can think of, hope it helps
...I finally looked at my SDCard via my brother's phone.
Every thing in my SD Card pretty much has "Font" in front of it in regards to the name.
I mean... Yahoo became FontsYahoo.
wat
Solved.
For those who were wondering, I found out that I had to rename the recovery file to the PBNASFASodhwhatever it was.
So, I had been using my A500 for the last few days with no problems. Well, yesterday, I got home from work and powered it on. The lockscreen came up, but the screen was unresponsive. I turned it off and then back on, but screen still didn't work. Then I did a hard reset, which still didn't fix the problem. I put it into recovery, then did a wipe that still didn't fix the issue. I flashed the ROM again. Then a different ROM. All it does is is boot up and go to the lock screen, but the screen does not respond.
If I can avoid it, I don't really want to go through the hassle of returning it since I got it online. Hopefully it can be fixed without having to take it back. Thanks in advance for everyone's help.
Boot back into recovery.
Wipe your 3 things,
User Data
Cache
Dalvik
Then go to Mounts
Format the same 3 (user data, cache partition and Dalvak.
And Flexrom
Then flash your rom. Try and flash a basic rooted rom. No kernels, no gapps.zip
See what happens.
If you have a file called update.zip, on your sd, I would delete it. And anything else there except for the rom.
sounds like hardware failure. Has the tablet been dropped or banged around. The connector on the digitizer could have came loose.That would mean void warranty and take it apart ..
Send it back is likely your. Best option
Thanks for the quick responses! I'm gonna try these things, hopefully I don't have to take it back.
Guess it is a massive hardware failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
sikkboy626 said:
Guess it is a massive software failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
Click to expand...
Click to collapse
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Moscow Desire said:
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Click to expand...
Click to collapse
Thanks for all your help. I was able to get it back to stock. The return should go fine. You're awesome and I did not forget to use the thank you button.
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
You can use normal usb mouse with this tablet, you will get mouse pointer on the screen when you connect mouse...
erica_renee said:
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
Click to expand...
Click to collapse
I was able to flash using the physical buttons. I got it all back to factory specs so I can return it. you were correct I believe, it does seem to be a screen hardware failure. Everything else works but the touch response.
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
erica_renee said:
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
Click to expand...
Click to collapse
Guess I had to take one for the team
Ill start this saying, yes, im a noob. I rarely post or visit unless i have problems.
But i do have experience rooting this specific phone before. But this time around its giving me a LOT of problems...
Ill start with:
Samsung Epic 4g (D700.0.5)
FM 2.3.6 (GB)
BB EL30
K 2.6.35.7
Now i will attempt to explain all the problems as well as what i have done to try to fix them and i will give as many links to the pages that i used for guidance as i can.
As i said, i have experience rooting this specific phone in the past. I ran a stock rooted ROM and everything was fine other then some glitches that i just learned to live with. But about 3 months ago i got a few more problems that have been driving me crazy so i desired to reroot.
When i power down the device, it will not turn back on just by pressing/holding the power button. Removing the battery, reinserting it, and holding the power also dose not work. I finally figured out that i have to remove the battery, replace the battery, then quickly (before the on-screen battery disappears) insert a charging cable thats connected to a power source. Then when the battery turns green (even with minimal power or full power) i can then power it on, but only when the on screen battery shows green. If i wait too long and it disappears it will not work and i have to start over from the beginning. (Removing Battery...) That was the 1st problem.
Soon after this happened (maybe 1-2 weeks) my phone started doing random shutdowns and not powering back on (i assume because it didnt have a power source connected). This would happen at anytime of the day or night, even when it was connected to a charger and actively charging. Yesterday i finally had the last of it and started researching this problem. I found that apparently some/all of the epics have this problem in time. From what i read the micro(or mini im not sure) USB port dosnt fit 100% snugly. So it causes heat. This heat causes corrosion and eventually leads to this problem. (I have never got this phone wet in the 1.5 years i have had it, i take very good care of my electronics.) Around the time this started my phone also would drain its self in about 2-3 hours, this was due to it constantly thinking i was plugging and unplugging it from a computer and requesting that i choose from the 3 options of mass storage.... Eventually the whole screen turning black with the android and the 3 buttons went away but the pop up on the notification bar continued, and as already said, it will drain the battery quickly.
NOW on to the rooting problems.
I dont remember what rom i was running originally, but following a few videos from QBKing77.
I odin'd back to EC05. This went fine no problems. (Useing odin 1.85)
I then tried to use the e4gtauto.zip file and running the "RUNFIRST.bat"
Used option A (install Root not EL13/newer)
Everything went though like it was suppose to. No errors or problems. Phone rebooted into recovery rather then to the lock screen.
Not remembering how to use recovery, i did some research, apparently the camera button is SUPPOSED to be the select button, but this did not work for me at all. After several manual reboots (pulling battery) this was the only thing i could get to (not even download mode to try to flash back to EC05 again). I did some research and found a post that said the "home" button on the front of the screen was his selector for some strange reason. This worked for me. I selected "reboot now" or something like that (the 1st option) and it rebooted into what i was thinking was a rooted rom, checked and there was no SU, or BusyBox (as said would happen in the e4gtauto).
I downloaded an su.zip and figured i would flash it with CWM (last time i installed CWM it was "purple" or 3.1.0.1)
Well it seems that my CWM is gone... i did the ever famous "3 finger salute" of Vol Down + Camera + Power and nothing except that i had to select "reboot phone" again from what i believe is stock recovery. Which booted me back into EC05.
By this time it was late at nite (2am or so) so i went to bed, over night apparently it updated and is now EL30. Thinking this was a good thing (and deff proving im not rooted) so today i tried rooting it as EL30.
Still do not have CWM seemingly.
Also would like to note, inorder for me to get to download mode, i have to take out my SD card, take out my battery, plug in the phone, and hold 1+power when the green power indicator comes on as stated above. This is the only way i can get into DownloadMode (if that helps at all)
If i could get any information on how to root from EL30 i would appreciate it greatly!!!
I will answer any questions as fast as possible, and i will provide as much information as you request when as soon as possible.
Thank you all in advance.
LATE:
Im not able to post links... so i cant give all the steps ive followed so far, I have attempted to take out all infomration already stated related to a link or video... Sorry.
I can do this for you remotely via teamviewer 7 google it and install it pm me the id and password and ill do it all for you
Oh and you used the epic touch one click root... not ours.. and el30 doesn't work on one click root.
Sent from my SPH-D700 using xda premium
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
YourLordAndMaster said:
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
Click to expand...
Click to collapse
You have the wrong recovery installed... you used the epic touch one click root... ... just go get teamviewer and ill fix it for you.
oh but now your on stock recovery because samsung has a script in the kernel to restore the stock recovery upon boot.
The rooting has been fixed.
I didnt install a CWM file apparently
and i also did a lot of bad things
Big thanks to "Big Goron" for the help he provided
Hey, Thanks for taking the time to help.
Device: Nexus 6P
Previously Working ROM: Pure Nexus
Recovery Type Was: TWRP
So, I was on Pure Nexus just fine and decided okay! It's been a few updates I'll just update to the newest version. Went ahead and did a Clean Flash, wiped everything in TWRP except the Internal Data, proceeded with a Flash for the new Vendor Image and then to the newest ROM. Restarted and an immediate boot loop.
Thought okay, whatever. I'll just use the my backup that I have! booted into TWRP did backup.. still boot loops. At this point I'm pretty upset cause I know I'm in a pretty terrible spot now, so I decide to do a Factory Image complete restore through Fastboot flash-all.bin.
CONTINUES to boot loop after that, also doesn't even install the stock recovery or something because after a stock flash it shows "No Command". Decided okay, I'll flash TWRP and attempt a factory reset in there, do so. Still boot loop.
So yeah, here I am.
Any advice?
The bootloop of death may have caught up with your phone. When did you get the phone, you may have to rma the device. There is a thread here that many have the same issue. Some have gotten rma out of warranty some didn't. You may want to try.
Hey, the "No Command" is actually stock recovery. You should see the Android on its back with it's chest plate open or something like that. A red exclamation mark in a triangle as well, IIRC.
When you're on that screen, hold power and press and release volume up and that'll take you into stock recovery. If that doesn't work, do it the other way around. Hold volume up and press power.
If you can get into stock recovery, you should be able to use ADB to pull your files, at least.
My 6P screen crapped out yesterday and I just had to pull data myself, let me know if you need any help.
Thanks for the replies, still stuck in a boot loop even after trying another Factory Image in case the one I got was just no good.
Still nothing, was able to get into the recovery even with the no command thing to Factory Reset/Wipe Cache and the problem still persists.
I'm at a loss at this point, I even tried to flash each file in order manually instead of with the flash-all command anddddddd nothing In the end, I'll probably try and RMA since I'm still within a year.
Anyone been through the RMA process want to give any tips on the process? Should I re-lock the boot loader before sending it in?
Don't even bother, you're screwed basically. Call Google or Huawei were you bought it from and ask for a out of warranty RMA. I got mine only last week after they had it for a week. Prepared to be given the run around if this is with Huawei. Google is currently out of 6P's so you might be given credit if you bought from them, that's a big BUT. Good luck and I hope you have a backup of your files off the phone.
bammyman said:
Don't even bother, you're screwed basically. Call Google or Huawei were you bought it from and ask for a out of warranty RMA. I got mine only last week after they had it for a week. Prepared to be given the run around if this is with Huawei. Google is currently out of 6P's so you might be given credit if you bought from them, that's a big BUT. Good luck and I hope you have a backup of your files off the phone.
Click to expand...
Click to collapse
Actually, I'm still within the 12 months. But I know that the whole Custom Rom thing kind of voids that. I did end up calling Huawei and ended up getting the in-warranty RMA started but... kind of scared cause I'm not sure if the whole flashing the thing with a non-offical ROM gets flagged some how.
Should I call back and specifically request an OOW RMA? Or just take my chances with the In-warranty RMA?
They do not care about custom roms. Just send it in with a factory reset. I sent mine in with Android O and they were fine with it
I'm sorry I don't know who to turn to for help. I have a Nexus 6p and it is stuck in bootloop. I'm phone illiterate so I don't even know how to go about fixing it. There are very important photos and voice notes on there of my father that I would like to preserve as they are the last things I have of him before he passed away. Willing to pay $ to get this fixed. Any ideas?
BB12345 said:
I'm sorry I don't know who to turn to for help. I have a Nexus 6p and it is stuck in bootloop. I'm phone illiterate so I don't even know how to go about fixing it. There are very important photos and voice notes on there of my father that I would like to preserve as they are the last things I have of him before he passed away. Willing to pay $ to get this fixed. Any ideas?
Click to expand...
Click to collapse
Are you able to get into recovery?