[Q] Phone stuck on bootscreen after build.prop changes - Android Q&A, Help & Troubleshooting

I've been searching the forums, and google for a while and can't seem to find a solution that works at all for me. First off, a little history. I am a n00b, and I very stupidly rooted my phone last night, without a recovery.... Actually I don't think just rooting was a big deal, it was me changing the vm heap properties that was really stupid. Why did I change it when the phone was working fine you might ask? Because I quickly gleaned over a forum post about adjusting the heap size to make your phone blazing fast, so, like any other idiot would, I did what the thread suggested, and instead of blazing fast speeds I got a boot screen logo....... forever... Talk about a huge mistake on my part....
Here's the problem,
Phone is stuck on the bootscreen, I can boot into system recovery (stock).
Android System Recovery has a message on the bottom of the screen that says "E: Cannot load volume /misc!"
I have wiped the cache partition, and did factory reset according to the manufactures website.
I cannot get ADB of Fastboot to see the device, even with drivers installed.
I do have a back up of build.prop that is unscathed, but I have no idea how to flash it, or "push" it or whatever.
I do not have CWM installed, and it appears that usb debugging is disabled.
My phone is a Kyocera Hydro. I'm using Windows 7 64bit.
I know I should never have done this, it was idiotic, and easily the dumbest thing I've done in a while. I'm hoping someone out there can help me fix this. Is it possible to put the backup of build.prop on the SD card and have it overwrite the corrupted one? Is there any hope at all?

I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.

Well right now you're pretty screwed. There's no way to restore it without a custom recovery. You have 2 options -
1) Wait for someone to make a custom recovery for your phone.
2) Try to claim warranty and get it restored/exchanged at the service center. Say it just randomly rebooted and got stuck at the boot screen.
Sent from my Desire HD using xda premium

Aravoth said:
I guess it can't be done then? I had hoped that as long as the bootscreen could come on that there was hope. Hopefully someone out there knows how to push the backup build.prop back onto the phone.
Click to expand...
Click to collapse
Where did you get the phone Boost, Amazon Wal-Mart?
Sent from my KFTT using xda app-developers app

Related

[Q] Used Tenfar's CWM to Format & Partition, Touch Screen Off

Hi, I'm trying to help a fellow Atrix user after he formatted and partitioned the internal flash memory using Tenfar's CMW Recovery.
He has lost touch on the bottom part of his screen; about a 1/2" of screen space doesn't work.
Tenfar posted that he had done this too, and had resolved this by reformatting with the Stock Recovery. Another user asked in that same thread how he accomplished that, but no answer has been given yet.
This user cannot get the Recovery Menu to show up because of the lower touch screen not working.
Can the steps be run blindly without the Recovery Menu showing up?
Or, can someone help me on how to have him format the internal memory via ADB?
I've had him try the following ADB commands from both the /!\ Recovery Screen and after enabling Early USB Enumeration without luck.
Code:
adb shell
$ su
# format DATA:
Comes back with format: not found.
Can anyone help? I've seen a few others with this issue but have yet to see a full solution posted for those that aren't ADB experts.
I have this problem too! Tenfar was kind enough to try helping me but apparently I'm a retard and unfortunately can't follow his instructions. I've been spending an entire week reading hours each day and I'm embarrassed that I still can't fix it, despite him sending me almost a dozen PM's trying to do so. Very grateful but sad that I'm so dumb.
He's told me to do this:
$adb shell
$su
#busybox umount /sdcard (hit enter key)
#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18 (hit enter key)
I'm not sure where to do this. I now think I do this while the device is in Early USB Numeration but I haven't tried it yet. The wife was getting really pissed because I spent the entire weekend trying to fix this and have been investing too much time on the computer. She's... having mad PMS so I'm leaving it for a few days lol
I tried earlier when the phone was booted up but after some research, believe it may need to be done in Early USB Numeration mode but there's only about a minute before it automatically reboots. I haven't tried this and hope that my assumption is correct. I know about 3 other people who are currently experiencing this challenge and I hope that it corrects it.
The wife is working a double shift today so I'll try after work. Can't blame her for getting upset with me. Soft bricked a few other phones but fixed them with relative ease. This has been by far the toughest. It was my birthday last week and I spent most of my day on the computer trying to fix my Atrix lol
After this, no more formatting internal SD partitions!!! Paypal is giving me grief but I plan on giving Tenfar a modest donation. He's been very supportive of my dumb ass lol
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
coldfusionb said:
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
Click to expand...
Click to collapse
Thank you!
I managed to install Ubuntu and I really like that.. tried from there too and it wasn't working. So I think it's definitely a problem with my dumb ass. If and when I get it working (I'm determined!...... and sort of stuck lol) then I'll post a guide.
Fuuuuuuuuuuck!!! Still not working!!
Yeah.. i ended up wiping with stock recovery and still a no go. Still no lower half of the screen or buttons. Sucks big time
Once ADB can be run in the recovery menu I think it should be fine.
Tenfar said he's fixed this problem but I'm no sure where he's run these commands. I feel bad after sending him a ton of PMs so I'm just waiting until he updates his Recovery app.
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
sgtmedeiros said:
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
That's been mentioned and tried multiple times.
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
das8nt said:
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
Click to expand...
Click to collapse
There's still a glimmer of hope, buddy. Once we get ADB access in Recovery I think all should be well.. unless partitioning this block somehow corrupts and kills the digitizer or something.
I actually couldn't wait any longer. Ported to Bell and got a new Atrix so if things go bad I'll have an easier time swapping. When I fix this AT&T one I'll sell it to pay off my cancellation fee with Rogers. Or, if I end up sending it to Motorola I can go back with my buyer's remorse period and go back to Rogers.
Hope you've got a backup phone or something to use in the meanwhile, man. This issue drove me INSANE!!
Hope is good, but this isn't necessarily for me. That's why I can't test it; this didn't happen to my phone. I have just been trying to help those who this did happen to. I'm also sure it will continue to happen if the CWM port for our phones isn't preset to format correctly.
Glad you were able to get a working phone again, but too bad a phone had to go back under these conditions.
Well, I'll keep trying to figure it out; waiting on another reply from Tenfar. Our schedules don't mesh too well, so if there's anyone else that might have experience in formating via ADB any help would be appreciated. Thanks!
Sent via rooted Moto Atrix using Tapatalk
I have the same problem, I just wanna know if anyone found a solution to fix that?
Also, I live in Belgium (Europe), I bought the atrix in usa a month ago during my honey moon. Motorola Europe doesn't support yet the atrix, I don't know what to do!
The phone is not usable anymore, like someone said: "clicking on the soft button area registers as a click on the bottom of the screen". So, the back button don't work anymore (you have to reboot when your stuck in a menu!)
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
what if we execute the script using the update.zip function?
i can access my sdcard from windows in storage mode
if we put the script in one signed update.zip into the sd the phone should be able to execute itself?
KeRmiT80 said:
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
Click to expand...
Click to collapse
Tenfar told me it was mmcblk0p18 but it's actually mmcblk0p03 which needs to be corrected.
There's no ADB in recovery right now. Tenfar's apparently got it working but hasn't released it yet.
I also guarantee you can bypass the Motoblur setup as well. Hit these keys:
?123
ALT
ABC
e
?123
ALT
ABC
e
b
l
u
r
o
f
f
I'm positive because I've literally flashed every SBF and I've spent a lot of time troubleshooting this issue.
really i cannot open the keyboard while i'm in the blursetup screen, i keep pressing the menu button but it highlights only the emergency call and after many seconds it chance to emergency call screen...
At this time, your phone is 'bricked' since we can't get ADB access.
Sent from my MB860 using XDA Premium App
we don't have adb access but i tried and we can use the update function in the stock recovery...i tried to put a update.zip of my old milestone and the process worked till the sign verification that failed.
in the milestone that update.zip is used to run the updaterscript that launches the openrecovery by skrilax_cz, that works like the recovery of tenfar
i guess that if we have a correct update.zip for atrix and we put in it the script we need, it should be run.
unfortunately i don't have the knowledge to build the correct script and don't have access to a signed update.zip for atrix.
if we only could gain some interest of the devs i think our problem could be solved in short time...
edit: i sent 2 pm to tenfar but did not reply, maybe someone has more luck...

[SOLVED] LG Optimus V - Blank Screen

I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!

[q] Atrix not starting past M Dual Core screen - Long boot time

Hey all,
I did my searching for the last several hours, and am feeling pretty weak. I know there are several other posts with this error - but please let me explain my situation.
Phone was running 2.3.6. I am unsure how it was originally unlocked (carrier unlocked) and bought it used. To my knowledge it did not have root access... (though the advert said it did - running SU in Terminal to show if it had access failed)
I tried doing a factory reset on the phone because it kept acting weird. Just rebooting 10 times a day, and wifi not working either.
Since the reset the phone has not made it past the M Dual Core screen.
Edit as I type: As I type this, I FINALLY got into recovery mode. It took a long time... is that normal? I mean.. loongggg. Now i see other posts state I just need to click the bottom right corner above the search key and I should be on the way to recovering the device...
This however is not working...
I will keep the phone plugged in over night and see if it just needed more time I suppose. Can you guys recommend anything?
I am on win7 - should have the device drivers installed (though, Windows doesn't seem to recognize this with a notification bubble). I know the phone was not on USB Debug Mode when I clicked 'factory reset'.. would it have retained this?
I will update as i have more information.. otherwise if I am missing something please let me know.
Thanks again,
-k
Try booting into recovery mode by holding volume down while turning on. When the menu appears keep pressing volume down until it says android recovery and then press volume up to select it. If an android Guy with a warning sign shows up, press volume down and up. A menu should appear soon. Try to do a data wipe and factory reset from there.
Sent from my MB860 using XDA App
Hi ar31791, thank you for the reply.
That worked to put me into a recovery mode - very nice. Is the button combo different depending on the version of android your'e running, or just phone dependent? I appreciate that.
Couple follow up questions if you guys don't mind and can help
- after the factory reset - my boot time is incredibly slow.... like 30 minutes to boot kinda thing. I tried to factory reset several times since, and its the same issue.
- my data is not working on the phone. I used the apn suggestions from all sites I've found, rebooted (took a while) tried data roaming, etc, but it just doesn't work. I have a decent idea that the apn's are correct because the mms apn worked fine with a test picture message.
My main concern is the incredible lengthy boot time and the data no longer working. The issue with wifi still showing 'error' when enabling it was not resolved by the reset (I didn't think it would - I was reading other posts where it is suspected as a hardware issue).
Thanks again for the reads, and replies. I appreciate the help!
-kenny
You need romracers or cwm. Unless yer going to stay stock.
Sent from my MB860 using xda premium
Is this an att or a rogers/international phone? Best bet would be to flash pudding and than cwm + custom roms
hey again- thank you for the replies.. seriously. much appreciated.
phalanx, i dont mind staying stock but would that not allow the data connection to work correctly? i found a few posts based on the romracer. i lack the hands on experience, but it looks like i just need to follow the steps for an adb push and then install eh?
you mention staying stock, is that an option? info on my setup below
crnkoj, i am running a bell phone on a fido network in canada. bought on ebay pre unlocked. i do not bekieve it is rooted. phone, mms and text work fine, it seems to be a problem finding a data network at this moment.
thanks again guys, ill be taking a look into the tutorials for romracer and cwm, and giver a shot. lemme know if you have any further ideas, questions or anything you think i might need to know.
edit.. also, whats the deal with the crazyyyyy long boot up time?
kenny
(send from a mobile.. please excuse any typos or punctuation errors)
No its just that with an unlocked bootloader you can flash a new.recovery and that makes it easier to flash roms and also kernels and radios. Kernels and radios can affect your ability to connect with data and can even affect the speeds.
Sent from my MB860 using xda premium
I had a similar situation. So, i did a full wipe installed the rom did another full wipe then installed the appropriate kernel and booted it up. I believe you nedd to install the right kernel per the instructions. It will mot boot if the kernel is not correct.
Sent from my MB860 using xda premium
Thanks again guys,
Man it's a funny issue. I am always able to get in and factory wipe the device, but it seems that sometimes that damn M screen will sit forever. I left it over the course of a movie and a half (probably 3 hours) and that screen was still just sitting there.
I get into the fastboot menu easy enough before that screen hangs, and sometimes i can get into the Boot Android (without BP) (I believe it's called) and sometimes it hangs, and sometimes it works.
Other times, like right now, it boots just fine and kinda fast.
I am having an issue with the RSDLite application recognizing my phone. It did once - then hung at 94% flash of the pudding tutorial. I didn't realize the tutorial says to keep the phone plugged in for 10 minutes even after a fail to see if it actually completes. I havent been able to have the software recognize the phone since- I've installed and reinstalled the motorola drivers, set the phone to usb debugging, and was able to try 2 computers, and 2 different cables. I'll giver another shot though.
I am pretty sure my boot loader was unlocked (as I said I had this all done from an ebay purchase) so I think I can just proceed to the flashing, but if there is a way to confirm that it is indeed locked, I'll take the advice.
The more I read though, it looks like I might just need to send this beast in for a service call with Motorola, because of that damn wifi "error" error. I'd hate to go through all this and realize it still will not work.
Thanks for the replies, I'll always take more suggestions, and if you guys think I'm on the wrong path, let me know. I'll keep searchin dem' forums
If your bootloader is unlocked it will say unlocked in white letters on that M boot logo screen. Did you run "fastboot oem unlock" after the rsd flash?
Sent from my MB860 using XDA App

Is my Kyoceria Rise bricked??

I did a factory reset on my Virgin mobile Kyoceria Rise which i have done before, but this time something went wrong. The phone just continues to BOOT LOOP after it gets to the "flick to unlock your phone screen"
So it does boot into the OS.. just it reboots soon as the stock flick to unlock screen comes up. The only thing i changed with this factory restore is i froze/deleted some bloatware a couple months ago that i didnt restore before the trying a system restore on monday. Im wondering does this have anything to do with it or did something else get screwed?
I know i froze Virgin mobile setup which might be the issue, but i doubt it.
I already read there is no custom recovery for this phone and no clockwork because Kyocera has the bootloader locked down pretty good, so if something goes bad you have to send it to them or just get a new phone.
Also, i already tried the android restore by holding the volume down+power key and a selecting full data reset/restore but this still results in the same bootloop. Also says, "Cannot find /misc" which is normal i read.
Just wondering if my $50 android gone?
EDIT: i dont see a section for this phone so hopefully this is right.
I spent 3 weeks trying to fix my Rise which was also in a boot loop. I've looked everywhere and still havnt found a solution.....until kyocera agrees to unlock the boot loader we got paper weights but for me this was a great learning experience! I taught myself how to use adb and SDK. I have a Motorola Xoom and ive rooted it, bricked it, and unbricked it! I recently started looking around again for a solution to my Rise.... I have the stock image but I can't push it to the phone. I put my rise in recovery mode connect it to my PC but adb won't recognize it. So our best bet is hope that the boot loader will someday be unlocked......
Sent from my Xoom using xda app-developers app

Verizon Ellipsis 7 Unbricking?

I am assuming no one has bricked this device yet but I believe I just did I am rooted and stuck at a welcome screen if anybody has a solution please help! if not I'm going to the store Saturday and telling them a silly lie
Yeah I just did too :/ I installed chainfire 3D and now it stays at the Verizon loading screen. It doesn't shut off, only reboots to this screen. Safe mode doesn't work. I'm hoping there is a way to fastboot, factory restore, etc. via USB. But I think I'm SOL
I just went up to the Verizon store and play dumb I was able to get mine replaced
Sent from my HTCONE using Tapatalk 2
I figured as much. I talked to someone over the phone and they said to bring it in for a replacement. So I'm going in tomorrow for a new one. Lesson learned haha
Sent from my XT907 using Tapatalk
Really hoping someone has came out with a unbrick/really BootLoop of Doom...
So I know a little about android and learn quick and there is very little information on the verizon ellipsis 7. Just so happens I bought one from a side shop and figured out Framaroot will easily root this device. Well you can guess what happen from there. All was going well until i rebooted with rom toolbox pro to change the font format for the second time. Now ever since it hasn't made it past the verizon screen and i cant take it back. Is there any possible way at all of somehow getting a custom recovery on this thing? Or even better a unbrick/bootloop? Oh and I CAN get it to go into stock recovery. Tried the Clear eMMC and Safe Mode but no luck.
Im in the same situation, I'm not able to boot into safe mode and clearing the emmc (formatting /data) doesn't seem to help either. I believe /data is just the user saved data, system data remains the same and is still corrupted. I had rooted, installed xposed framework and a few modules, rebooted fine the first time, but when I went to go change a setting within Ultimate Dynamic Navbar to make the stock navbar hide or not to hide, the script it used killed the tablet and now my wife's valentines day present is stuck in a bootloop. I'm going to try and take it back to verizon tomorrow after work, hopefully I can get yet another free tablet from big red... rvajuggalo said he was able to get it replaced right away even though it was rooted, anyone think I'll be fine taking it back as well? Or should I just wait til someone comes out with a fix for this issue?
wonton9224 said:
Im in the same situation, I'm not able to boot into safe mode and clearing the emmc (formatting /data) doesn't seem to help either. I believe /data is just the user saved data, system data remains the same and is still corrupted. I had rooted, installed xposed framework and a few modules, rebooted fine the first time, but when I went to go change a setting within Ultimate Dynamic Navbar to make the stock navbar hide or not to hide, the script it used killed the tablet and now my wife's valentines day present is stuck in a bootloop. I'm going to try and take it back to verizon tomorrow after work, hopefully I can get yet another free tablet from big red... rvajuggalo said he was able to get it replaced right away even though it was rooted, anyone think I'll be fine taking it back as well? Or should I just wait til someone comes out with a fix for this issue?
Click to expand...
Click to collapse
I was able to get a new one and mine was stuck in a boot loop
Sent from my XT907 using Tapatalk
Elipsis Bootloop Help!
rvajuggalo said:
I am assuming no one has bricked this device yet but I believe I just did I am rooted and stuck at a welcome screen if anybody has a solution please help! if not I'm going to the store Saturday and telling them a silly lie
Click to expand...
Click to collapse
If anyone has a clean copy of the system or firmware directories can you please share with me? --- Also if anyone knows how to get into the stock recovery without android debugging please explain? On a final note if anyone has a custom recovery that they could share that would be amazing as well. I'm in a bootloop and have been stuck in it for a couple weeks. Any assistance would be most appreciated.
dduncan55330 said:
I was able to get a new one and mine was stuck in a boot loop
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Thanks, that confirms it for me, I'll definitely take it back tonight, hopefully it's in stock and not back-ordered
wonton9224 said:
Thanks, that confirms it for me, I'll definitely take it back tonight, hopefully it's in stock and not back-ordered
Click to expand...
Click to collapse
VZW made me send my ellipsis to them for the screen issue after update, i unrooted it before sending it. They were able to fix it somehow because they sent mine right back fixed(i wrote down the serial)
mtk_droidroot_backup_Verizonellipses...HERE
Backed up my QMV7B before i Bricked it, now ive got two mtk paperweights pm me ,I'll link you to a backup on my drive. also bookending my desk is a lovely alcatel oone touch fierce 7024n which proudly boasts "ERROR 101 This phone has been flashed with unauthorized firmware and has been locked." niether of these will respond to any flash utility ive been able to conjure
Maybe you can use it. I need some hands on guidance flashing these. way too many tutos,way too many fllashtools, way too many drivers, usb cables, homemade serial cables, linux distros ,windows xp,7,8,8.1, hours, days,weeks,....... you get the picture.
apt-get ME_A_STRAIGHT_JACKET!
I know it can be done, i would like to learn from someone who ddoes it. its taking way to long to teach myself. and i still kinda like my wife but i doubt shell take much more.
#BRICKED --help
dereksilvers said:
Backed up my QMV7B before i Bricked it, now ive got two mtk paperweights pm me ,I'll link you to a backup on my drive. also bookending my desk is a lovely alcatel oone touch fierce 7024n which proudly boasts "ERROR 101 This phone has been flashed with unauthorized firmware and has been locked." niether of these will respond to any flash utility ive been able to conjure
Maybe you can use it. I need some hands on guidance flashing these. way too many tutos,way too many fllashtools, way too many drivers, usb cables, homemade serial cables, linux distros ,windows xp,7,8,8.1, hours, days,weeks,....... you get the picture.
apt-get ME_A_STRAIGHT_JACKET!
I know it can be done, i would like to learn from someone who ddoes it. its taking way to long to teach myself. and i still kinda like my wife but i doubt shell take much more.
#BRICKED --help
Click to expand...
Click to collapse
Do you think I could get a copy of that backup file?
DYI
rvajuggalo said:
I am assuming no one has bricked this device yet but I believe I just did I am rooted and stuck at a welcome screen if anybody has a solution please help! if not I'm going to the store Saturday and telling them a silly lie
Click to expand...
Click to collapse
If you're willing to open the back plate. (Back plate just pulls off. I'd suggest opening the sim/sd card slot and using that to pull it off. You need to disconnect the battery wait a few seconds, reconnect and then boot into recovery.
1. Black plate removal
2. Disconnect battery
3. Wait a few seconds
4. Reconnect battery
5. Press and hold Power and Down volume button until you see "Powered by Android"
6. Release the power button continue to hold down volume
7. Once in Factory recovery mode choose your best option
(I just factory reset it)
:good:
-love
A new development, possibly.
dereksilvers said:
Backed up my QMV7B before i Bricked it, now ive got two mtk paperweights pm me ,I'll link you to a backup on my drive. also bookending my desk is a lovely alcatel oone touch fierce 7024n which proudly boasts "ERROR 101 This phone has been flashed with unauthorized firmware and has been locked." niether of these will respond to any flash utility ive been able to conjure
Maybe you can use it. I need some hands on guidance flashing these. way too many tutos,way too many fllashtools, way too many drivers, usb cables, homemade serial cables, linux distros ,windows xp,7,8,8.1, hours, days,weeks,....... you get the picture.
apt-get ME_A_STRAIGHT_JACKET!
I know it can be done, i would like to learn from someone who ddoes it. its taking way to long to teach myself. and i still kinda like my wife but i doubt shell take much more.
#BRICKED --help
Click to expand...
Click to collapse
After making edits in system files I broke my QMV7B. Hangs on powered by android logo. In a panic, I wiped emmc from factory more (Chinese).. This reset ADB keys, and complicated matters further. After some digging I may have caught a break... I have figured out a way to stop and suspend the tablet in it's pre boot, or preloader, state. While suspended, it maintains COM3 connection with SPFT, and does not power cycle on and off. It also successfully installs it's onboard Preloader driver without error. Problem is that I need help attempting flash (for best chances)...
needing stock 4.4.4 fit the qmv7, or possibly advice on stock recover if possible.. I have successfully flased devices with Odin before, and have rooted almost every I have had.. I just want the best chance for success, and not to full brick the tab.. this could also be a solution for newer devices as well, but would like to for a good developer to speak with me before I post my findings. I will also post if I get the stock room compatible for flashing with SP Flash tool.. thanks guys..
Help
Please post specifics on how you achieved suspending in Preloader mode. That would help me alot.
I really need the un-rooted qmv7a stock rom, if any one could provide, that would be fan-freaking-tabulous lol...
no, for real i need the stock rom. I'd really appreciate it.
BTW
if you wanna get clean root on this device, i suggest this- http://forum.xda-developers.com/showthread.php?t=2748169
(has nothing to do with my need for a clean start, that was my own carelessness...)
Bondaddict said:
Please post specifics on how you achieved suspending in Preloader mode. That would help me alot.
Click to expand...
Click to collapse
Needle point method at USB port
ellipsis 7
I root my ellipsis 7 and install clockworkmod recovery after reboot in recovery struck on boot loop and not even access on recovery mode plz help
anybody still own one of these? lol
---------- Post added at 04:59 AM ---------- Previous post was at 04:41 AM ----------
LoveAboveAll said:
If you're willing to open the back plate. (Back plate just pulls off. I'd suggest opening the sim/sd card slot and using that to pull it off. You need to disconnect the battery wait a few seconds, reconnect and then boot into recovery.
1. Black plate removal
2. Disconnect battery
3. Wait a few seconds
4. Reconnect battery
5. Press and hold Power and Down volume button until you see "Powered by Android"
6. Release the power button continue to hold down volume
7. Once in Factory recovery mode choose your best option
(I just factory reset it)
:good:
-love
Click to expand...
Click to collapse
Hey man it's been 5years & I just wanna say thank you for posting this as I just managed to get into factory mode thanks to your comment xD. factory mode didn't help me a bit but maybe when I get to a PC I can use mtk tools to get a shell or something from there. Thanks again and if anybody has anything more than what's on here about this tablet please contact me as I feel like the last human on Earth with one ????
Yeh
I have one??
And Reading all topics about rooting this tablet...i'm afraid to do that?

Categories

Resources