So I bought a Blu Studio 5.5 unlocked from boost earlier today and decided to mess around with it. I rooted and installed a clockwork recovery made for the device. I then flashed a supposedly ported version of MIUI for it too (stupid idea). The next boot did nothing but get stuck at the BLU logo. I've tried flashing two different stock roms to no avail. Now it is just stuck in a bootloop. I also seem to have lost root and cannot reboot the phone unless I removed the battery. I get the " Root access is missing. Root device. THIS CANNOT BE UNDONE" And then no and another option that is cut off and I can't even select the 2nd option. I stupidly don't have a backup image to restore with.
Is there anything I can do or have missed to potentially fix my stupid mistakes?
Related
Okay, here's the deal...
I've searched everywhere for every possible way to get around this and it still doesn't work.
I'm on a Mac (OS X 10.6). It says my phone is rooted (used z4root), then I downloaded busybox, and ROM Manager and Astro. i did the flash for clockworkmod through ROM manager, said everything was good. I try to go into recovery mode, reinstall packages, then I get the error "failed to verify whole-file" type thing. my recovery mode is 3e, and it's blue but from what i've been reading, it should be green? I'm trying to make it green!
I just got my captivate i896/i897 a couple days ago, so I wont mind if i need to restore it (i accidentally did that today but it still ended up being rooted when I finished). I'm brand new to all of this, the most experience i've had with this is..jailbreaking an iphone 4 lol. Any help would be much appreciated! All I want to do is make my phone faster (overclock it) and set a nice theme on it. This is so confusing and I'm starting to get so frustrated with it, close to the point where i'd throw it against a wall...legit. Please help!!
As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
CrimsonKatsuro said:
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
Click to expand...
Click to collapse
The solution may be a debrick image. They are designed to boot the phone from an external sdcard and from there reinstall the stock rom/firmware. I haven't searched yet, but check the general and development threads, possibly the stickied summary thread.
Check this thread
I have a original rom kyocera hydro c6530n rooted and used lucky patcher and messed things up royally from there after installing or trying to rather modded play store never worked all kinds of google errors gapp, service, no network connection and than no play at all applied all (as far is google concerned) fixes. never back to normal need less to say i uninstalled reinstalled all kinds of play stores reset rooted device to later find out I dont have any clue what I am doing obviously. I have reset to factory and hard reset and now I am stuck in bootlooper because I thought that re flashing with flashify would be the answer and yes I may have to get a new phone because wow but I flashed a boot image from the system uid I think I figured they wont give me an option if not viable. So now i am boot looped I do think i know that i can download my original jellybean 4.3 and flash to this device which is another matter and how would i do this i thought odin but not for kyocera and i find that there is no custom roms etc or recovery for this device.
My quetsions are
1. where do i get the download for jellybean factory image
2. how would i install from pc (my computer recognizes it still)
3. can i install a new rom persay and again back to #2
Thank you so much
mjkuhne said:
I have a original rom kyocera hydro c6530n rooted and used lucky patcher and messed things up royally from there after installing or trying to rather modded play store never worked all kinds of google errors gapp, service, no network connection and than no play at all applied all (as far is google concerned) fixes. never back to normal need less to say i uninstalled reinstalled all kinds of play stores reset rooted device to later find out I dont have any clue what I am doing obviously. I have reset to factory and hard reset and now I am stuck in bootlooper because I thought that re flashing with flashify would be the answer and yes I may have to get a new phone because wow but I flashed a boot image from the system uid I think I figured they wont give me an option if not viable. So now i am boot looped I do think i know that i can download my original jellybean 4.3 and flash to this device which is another matter and how would i do this i thought odin but not for kyocera and i find that there is no custom roms etc or recovery for this device.
My quetsions are
1. where do i get the download for jellybean factory image
2. how would i install from pc (my computer recognizes it still)
3. can i install a new rom persay and again back to #2
Thank you so much
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. There are no specific forums for your device on XDA. However, you may ask for more help here:
Android Q&A, Help & Troubleshooting
Good luck!
Hi all,
Before you jump at me telling me I haven't searched the forum, I DID and I couldn't solve my issue even with these solutions. To get you up to speed on what exactly I did.
Briefing (not very important):
I was doing my own business and I was free, I use my phone daily and it served me well. But I noticed that the last security patch I got was on 2020 and got me thinking. Why not just use custom ROMs to update my phone and get a year or two from my MIX3 (2018). I just recently flushed my brother's phone (Samsung) with a custom ROM and I liked it. I already installed TWRP 3 years ago on my brother's phone and I just had to install a zip file and boom new Android 12 on a 2014 phone.
The problem:
after reading here on the forums, it seemed that it is more complicated to do. I'm up to the challenge, I have done it before and the reward is worth it.
+Unlocking the Bootloader
this was a bit easy other than the connection issues but I got it unlocked eventually. (use the QR code to sign it. it is much easier)
I had an issue where after unlocking the bootloader the phone didn't allow me to install TWRP and do a backup, it immediately went into erasing the entire phone.
+Installing TWRP
I downloaded the files from TWRP website and everything was smooth other than the Mi Recovery popping every time I restart (install Magisk to plant TWRP then remove it if you don't need root)
+The downhill
after restarting, the phone worked fine I installed all the apps and restored everything. Afterward, I noticed that the camera does not work. It gives me an error. I reinstalled TWRP again since it was reverting to its Mi Recovery and I think here was the problem I flashed the recovery.img into the boot partition by mistake (I didn't notice at first) but after going back to the command I saw I made a mistake and reflashed the recovery with recovery.img and installed the Magisk and everything was ok. At the initial start, the SIM and the WIFI are not working.
after several attempts at reinstalling different flashable stock ROMs, I saw that the issue is consistent. I read online that you have five .img files that control the different parts of your phone. I got tired and decided to reflash the stock ROM via the Mi flasher and get it back to stock.
Even after flashing the stock ROM, I'm still having the same issue.
I reflashed the modem.img in the modem and still wifi and sim card are not working
I read that some phones have an A/B partition and my phone does NOT have it.
I'M AT A LOSS I CAN NOT FIX IT. IT'S BEEN 3 DAYS ON THIS AND I CAN NOT FIGURE IT OUT!!
Ok, If anyone was passing by I think I found what was the problem.
First, check if your problem matches mine. Go to Settings and check your IMEI. Or just dial *#06# ,if your phone did not return with a number then you lost your IMEI number.
follow this guide and I hope it helps. this is only for some phones so don't try it, it might break your phone
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com