Hi, so I decided I wanted to root my blu vivo 5R, being the inexperienced user that I am, I wiped the OS. I really don't know how to get the stock OS working again, I've tried SP Flash Tool, but I simply run into errors such as "cannot pass bootrom start command" (I think it's because the phone doesn't have a removable battery), I also tried adb sideload to load the stock rom, but that gave me an error that says "cannot read". I could really use some help because I don't have many other options than this phone, Thanks in advance :good:
use different version of SP flash
I got same errors using latest version of SP. I used older version and it works perfect.
Related
Hi to all
I have a Samsung galaxy s6102 and some weeks ego I entered a code (*#*#2663#*#*) which supposed to update touch firmware but it failed and touch screen never worked again.
I couldn't repair my phone even by flashing ROM an kernal. I tried method mentioned in this topic but I discovered that screencast does not work on my phone,hence I used ADB shell commands to enter the code (*#*#2663#*#*).
unfortunately just after entering the code this error message pops up: "The application com.sec.android.app.lcdtest (process com.sec.android.app.lcdtest) has stopped unexpectedly. Please try again"
I retried with different ROMs and got the same error.
I am wondering how should I erase touch firmware and flash new one and why flashing ROM and kernel do not replace this firmware?
It would be very appreciated if anyone suggest another solution for my case.
solved
after about 6-7 weeks finally I found a solution for my problem
simply flash stock kernel alone (not all of firmware) by CMW. after that touch would work again and flash any ROM you like
download stock kernel from here
I'm having an issue with mine
Touch doesn't work no matter what kernel or rom I flash using cwm
Phone won't get recognized on pc no matter what cable I use or windows I use, and I have drivers installed properly
I seem to be stuck at the stupid welcome window where it asks that I touch the android to continue
Everything was working just fine when I was on stock, but I made the stupid mistake of not making a nandroid when I flashed lu Kat custom rom and now I don't know what to do anymore
Any help would be appreciated.
Hi,
I recently purchased a ZUK Z1 but it came preloaded with lollipop 5.1.1, does anyone know of any issue I will experience if I upgrade from 5.1.1 to CM13?
Thanks.
Yes...
1 small issue..
*applicable for dual sim - home and office type...
Can't switch off sim 1 or sim 2 one at a time.. You would have to either enable flight mode (both sim - no networks) or take out particular sim you want to shut down.
Other than that.. Cm13 is perfect...
Cheers for the reply Vikas.
Having now tried to install CM13 I find myself getting stuck at the stage of using ADB to "adb devices" the device code returned does not match what is listed on the Cyanogen site (0x2b4c), additionally when I run "fastboot devices" I get the error "no devices are detected".
Can you offer any advise?
Thanks.
manc007 said:
Cheers for the reply Vikas.
Having now tried to install CM13 I find myself getting stuck at the stage of using ADB to "adb devices" the device code returned does not match what is listed on the Cyanogen site (0x2b4c), additionally when I run "fastboot devices" I get the error "no devices are detected".
Can you offer any advise?
Thanks.
Click to expand...
Click to collapse
Try using tool all in one by maurinfrio
*all data gets erased while unlocking bootloader. Take backup.
Hi & cheers for replies,
The all-in-on tool by maurinfrio didnt work for me , miniADB seems like the only one that would detect the phone and thankfully allowed me to unlock the bootloader.
To install TWRP I ended up using Kingroot to root the z1 then install TWRP manager via playstore, this thanksfully worked and I can start the z1 in recovery mode into TWRP.
Now I am stuck trying to install the recovery ver of CM13, I cant get past the blue cyanogenmod logo, the one with the circle around it, stays there for 23mins and does not goes past it, any suggestions?
Thanks.
Did you flash gapps...
Try reflashing once again in the order as
1. Rom cm13
2. Gapps
Then reboot.
*Wipe all except internal storage
*Take backup (Optional but recommended).
#if this doesn't help, I am not qualified enough to answer.
Hope this helps.
cm13 via twrp does not complete, so can't even get to the point of installing gapps.
Not to worry Vikas, I'll keep researching.
Thanks.
manc007 said:
cm13 via twrp does not complete, so can't even get to the point of installing gapps.
Not to worry Vikas, I'll keep researching.
Thanks.
Click to expand...
Click to collapse
Did you install the right twrp?
I installed TWRP bootloader onto my OEM Unlocked Samsung Galaxy Core Prime G360P Via Odin, and afterwords attempted to boot into Bootloader.
Upon doing so the phones screen goes black, and it acts like its turned off. My computer can't detect it with ADB, and I can't boot it back on without removing the battery and then inserting it again, after which it boots normally.
So yes my phone is working, but I need to get the bootloader working, I don't even have the normal android one right now because of this odd bug, i have rooted phones and tablets before both via Kingroot, and ADB depending on the needs of the device, and have some slight experience with it but limited technical knowledge, i have found seemingly similar problems but all said to solve via ADB, which doesnt really work as my ADB cant detect my phone when it is in this dead state it goes into instead of bootloader.
I would like a fix that will allow me to have TWRP installed, nothing that requires root as i have attempted all one-click rooters and none work for my phone, and i cannot install a custom OS as I am on textnow wireless and getting it to work with one is the biggest pain on earth (plus my calling would become sh^te without the custom textnow rom calling)
So basically i need to fix the bootloader without installing a new OS altogether, without deleting any of my inbuilt apps, and without factory resetting as I cant get to the bootloader to factory reset anyway, honestly i just need a way to get TWRP to work. If the answer involves another way of rooting my phone via Odin (yes i can still get to the odin downloader) and then running a root requiring app to fix my recovery thats fine but i dont know how to do that or what it would entail
im using: twrp-3.0.2-0-cprimeltemtr
Textnow wireless uses a custom os that is slightly modified from the default, I don't know what that entails but i know that affects what fixes may/may not work so i am mentioning it
before i get the same answers i have tried:
redownloading TWRP and flashing the new copy instead in case of corrupted image
removing the battery after flashing and then booting directly into bootloader so as to stop it restoring anything
I have tried flashing other recoverys, however upon doing so found that when i tried to boot into the bootloader it would then boot to Odin instead and give me an error saying it was unable to boot normally, so i reflashed the TWRP one and it gave me the same blackscreen once again.
Any advice would be very helpfull, im at my wits end and id like to be able to recover my phone should it have problems later, id much prefer i not get stuck
Software Version: G360PVPS2APE2
Hardware Version: G360P .03
Model #:SM-G360P
Android Version : 4.4.4
Android Security Patch Level: 2016-06-01
Kernel Version:2.10.28-675169
Build #: TNG360PVPS2APE2
SOLVED
http://forum.xda-developers.com/gal...ime-sm-g360p-root-t3217885/page2#post70113291
I found something that worked highly reccomend this autoinstaller for Odin
Search the forums for stock rooted deodexed sm-g360p, thats the TWRP that I use ... almost to much. The rom is also alot more susceptible to root,mods,and tweaks. The rom is sprint, boosts a sprint partner. Its helped me get the 4glte i couldnt pickup with the boost. But definitely find that post. Twrp isn't official to our variant(that i know yet) but it works the same tho a lil dated.
Hi All,
I had given this BLU R1 HD to my daughter and I am not sure what happened but it started acting weird.
I used the recovery to load back whatever firmware was on the device but when I get to the 'Welcome' screen, connect to wifi, accept privacy settings, then the google account,no matter what google account I use, the phone won't let me proceed. It's asking me to verify my google account and I tried all the accounts that had ever been on the phone.
I am not sure what version I am on or if there is a way to find out using adb or something like that since I can't get past the google log on screen.
While in Recovery, it says the following:
Android Recovery
BLU/full_p6604/p6601
6.0/MRA58K/1522048061
user/release-keys
<options list>
Supported API: 3
I've tried using all the SP flash tools' firmware packages to see if that would fully reset the phone but none of the firmware packages of 6.4, 6.5, 6.6, 9.0, or 12, works with the SP Flash Tool.
Can you please recommend next steps?
Thank you.
revtek said:
Hi All,
I had given this BLU R1 HD to my daughter and I am not sure what happened but it started acting weird.
I used the recovery to load back whatever firmware was on the device but when I get to the 'Welcome' screen, connect to wifi, accept privacy settings, then the google account,no matter what google account I use, the phone won't let me proceed. It's asking me to verify my google account and I tried all the accounts that had ever been on the phone.
I am not sure what version I am on or if there is a way to find out using adb or something like that since I can't get past the google log on screen.
While in Recovery, it says the following:
Android Recovery
BLU/full_p6604/p6601
6.0/MRA58K/1522048061
user/release-keys
<options list>
Supported API: 3
I've tried using all the SP flash tools' firmware packages to see if that would fully reset the phone but none of the firmware packages of 6.4, 6.5, 6.6, 9.0, or 12, works with the SP Flash Tool.
Can you please recommend next steps?
Thank you.
Click to expand...
Click to collapse
Any luck?
Hi,
the other day a friend gave me her old Samsung tab 4 7.0 (SM-T235). It's in its default state, running Android 5.1.1 stock ROM with all the most recent (5 year old) updates. "KNOX" appears to be ok, afaik.
This is my first Samsung device, up to the date I had experience with HTC Desire, Sony Xperia (2x) and OnePlus devices. I unlocked / rooted and installed custom ROMs on all of them.
Done quite a bit of googling and playing around with my "new" Samsung to see where it's different compared to my other devices. But there still are some blank spots, and there doesn't seem to be too much information out there regarding that specific tab 4 device. Before I start messing around I'd love to have some input from experienced Samsung users in regards to custom recoveries and ROMs, and possibly rooting. If there are comprehensive guides etc. out there that I simply didn't find don't hesitate to give me some hints:
First of all it appears to me that this device is going under the codename "degas". Correct? (meanwhile confirmed)
I hooked up the device to my PC, made sure that adb found it alright, then called "adb reboot recovery". That worked nicely, got me into Samsung recovery
Next I again tried to connect through ADB to the device still being in recovery, but that didn't work. To be expected?
Still in recovery I chose the "boot to bootloader" option, but that got me back into system instead.
So from system I again connected to adb then called "adb reboot bootloader". Device booted alright, but again it just rebooted into system.
>> Is there really no way to get into bootloader?
Trying to find out what has to be done in order to flash a custom ROM (rooted or not): from what I get, and unlike my other devices, I do not have to unlock the device / bootloader to begin with. It looks as if it was sufficient to boot into what they call "download mode", then hook up the device to my PC where ODIN is waiting already. Following this thread (and others) it then is sufficient to just flash TWRP from ODIN, boot to recovery and then do what is usually done here (like flash custom ROM, flash Gapps and possibly Magisk etc.). Is there something else / important I should know / observe?
Speaking about TWRP and Custom ROMs: TWRP.me lists that device on their site. So has anyone here flashed latest TWRP (3.6.2_x)? Or should I rather start with an older version like the one listed here, then possibly upgrade from there?
In regards to Custom ROMs I basically just found this LOS 16 thread (which is the same linked in the previous "TWRP" bullet). I assume that's it, or does anyone know about a newer android version (which I didn't find so far)? There seems to be lots of activity around "matisse" and "millet", but apparently those aren't the right devices, right?
Back to recovery: I see that in stock recovery there is an option to "wipe data/factory reset": should I do that before flashing TWRP from ODIN, or is it sufficient to wipe everything once I booted into TWRP?
I'm aware that I'll lose "Knox" as soon as I flash a different ROM / Recovery. As I don't want to use the tab 4 in some critical "BYOD" area I don't care (neither do I care about warranty, that's long gone anyways). But just to be sure: is it true that I'll lose "Knox" access?
In case I would decide to "go back" to stock ROM one day, how would I proceed then? Would ODIN still work so that I can flash latest stock ROM? Would Knox then be restored, or is that a thing of the past once I leave the stock ROM path?
Again: if you think I've done a bad job searching for answers don't hesitate to let me know but please be so kind then to hint the phrases I should look for ("SM-T235" really doesn't bring up that much valuable info)
Thanks and cheers
Update 2022-08-03: meanwhile I realized that the device is connected to my PC through generic drivers. Would it help to install specific Samsung drivers although both ADB and ODIN are acknowledging the device? Or can I just neglect that?
Since no answers came in I dared to just try. Meanwhile I'm running the device on LOS 16 with TWRP 3.5.2_9. Then flashed MindTheGapps (arm/Android 9 flavour)The switch wasn't as easy as I expected for some reason not obvious to me (somehow I couldn't get into TWRP after flashing it through ODIN. Then after the ~25th attempt it suddenly worked). Meanwhile I installed the official Samsung drivers, and maybe that helped, in combination with other adjustments I lost trace of...
I'll answer some of the above questions, for anyone who's interested:
#3: while in recovery (TWRP 3.5.2, as it is now) I still cannot access the device through adb. But I have access from windows' file explorer, so at least I can exchange files while being in recovery. Strange thing, this is the only one of my devices that behaves this way. The other day I'll try again from a Linux machine. maybe that works...
#4/5/6: boot to bootloader still doesn't work no matter what I try - devices always boots back into system
#7: Once I managed to get into TWRP the rest was a breeze
#8: I tried TWRP 3.6.0_9-0 which worked but on every boot into recovery it shows first a red notice that recovery was not enforcing SEAndroid. The notice then turns into blue and a second later TWRP logo shows up. This dowsn't happen with TWRP 3.5.2_9, so I stay there for the time being. Then I felt lucky and installed TWRP 3.6.2_9 image from running TWRP recovery, then rebooted. That again showed the red "not enforcing" message - and got stuck there. Solution was to get back into "Download mode" then re-flash TWRP 3.5.2 through ODIN.
Conclusion TWRP 3.6.2 is not fit to be used on that device (no, I didn't try 3.6.1...)
#9: since there aren't any more security updates released by google for A9 ROMs it would really be great to be able to upgrade to an A10 or even A11 ROM... anyone ever tried to use a "matisse" or "millet" ROM?
#10: I decided to use that - wiping everything that was on the device then doing a factory reset as well before flashing LOS 16. Then after first boot into LOS 16 a strange thing happened: when I made a basic setting (in regards to location services" the device told me that in a previous version I had decided to NOT allow google to use those services: after all that wiping and factory resetting: how could the device know that? By that time I had not yet logged myself into Google. Very mysterious!
#11/12: I guess I know the answer: I'm out of "Knox" now once and forever. And apparently ODIN is still working and recognizing the device.
Cheers!