hey guys
im having problems trying to downgrade my phone to 2.1
im currently on andorid 2.2 - hboot 1.01 - 3.15
i have a goldcard and when im trying crackin.bat i keep geting this error:
cr--rw---- 1 1001 2002 90, 0 Feb 6 00:18 /dev/mtd/mtd0
also when i try to run the 1.31 ruu i keep geting a error saying the usb is not connected when it is..
also im a bit confused with the su thing
after temprooting my phone i go on adb shell- su but when i type crackin.bat at the # sighn it says crackin.bat is not found
but when i type crackin.bat at cd\AndroidSDK\tools it works but gives me the error message again (cr--rw---- 1 1001 2002 90, 0 Feb 6 00:18 /dev/mtd/mtd0)
please help iv been searching everywhere and i still have no idea what to do.
thanks.
First, make sure you have the old HTC sync installed.
I also got that error running crackin.bat. Like I posted in another thread right next to this one, you will get an error, you then follow this:
http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
You do not go into su and run crackin, you either open a cmd prompt and go to /tools/ of the sdk folder and run it or you can place it there and just run it.
The "USB Not Connected" issue could be that you might not have installed HTC Sync 2.0 (I sent you the link in a PM because I can't post it here for some reason)
If this solves the problem, try to continue the process with a temp-root and see what happens.
I hope this helps
Mafuzzer
im still geting the cr--rw---- 1 1001 2002 90, 0 Feb 6 00:18 /dev/mtd/mtd0 error even with htc sync
what am i doing wrong...
also im still geting the usb error even with htc sync
and im not sure what to do once i gained su permissions in adb...
help please
thanks
dilip007 said:
im still geting the cr--rw---- 1 1001 2002 90, 0 Feb 6 00:18 /dev/mtd/mtd0 error even with htc sync
what am i doing wrong...
also im still geting the usb error even with htc sync
and im not sure what to do once i gained su permissions in adb...
help please
thanks
Click to expand...
Click to collapse
Already answered, i (and many others) had the same error.
http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
The first post in that thread tells you what to do. Then continue on.
i finaly downgraded using blayos guide and im now sucessfully rooted again somomone please close this thread
Related
Hello everyone!
I apologize if this is not the place for my post, but I urgently need you.
I have an HTC Hero with Android 2.1 firmware.
The problem is this: using "adb shell" and having a temporary root permission, I do this:
mkdir /sdcard/sys/
mkdir /sdcard/sys/app
mv /system/app/ /sdcard/sys/app/
At the time of startup, the Hero always gives the screen "Quietly brilliant" all the time. It don't start!
Still using "adb shell" I tried to restore the data copied to the SDcard, but I do not have root permissions.
I'm desperate, I do not know what to do.
Can you kindly help me?
Thanks a lot.
htc hero
Make a GoldCard, downgrade your phone to 1.5, then root your phone and install a customROM!
Hi vnvio2005,
i try this step but i don't!
I downloaded and run RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe. The software start but write me this error: "Error [140]: Bootloader version error"
Please, help me.
Thanks.
Hi, I just purchased the new LG myTouch (all myTouches are now made by LG) from tmobile and I have been trying to root it with no luck. I have been trying to use superoneclick but it always gets to step 7 and stops working. I made sure my SD card is unmounted, the phone has USB debugging turned on, I have tried the pdanet method, and I tried unplugging and replugging the USB cord but it always stops on step 7. The phone has android 2.3.4 but I have seen other threads where people with 2.3.4 got their phones rooted so why can't I? Any ideas?
Sorry if I'm posting this in the wrong place but there is no forum dedicated to this phone. I'm guessing because it just came out this month.
i just got the Q for my girl, i was wondering the same, just to remove the bloat. can someone please point me to the right direction?
Just checking in to see if anyone has found any answers.
Network24 said:
Hi, I just purchased the new LG myTouch (all myTouches are now made by LG) from tmobile and I have been trying to root it with no luck. I have been trying to use superoneclick but it always gets to step 7 and stops working. I made sure my SD card is unmounted, the phone has USB debugging turned on, I have tried the pdanet method, and I tried unplugging and replugging the USB cord but it always stops on step 7. The phone has android 2.3.4 but I have seen other threads where people with 2.3.4 got their phones rooted so why can't I? Any ideas?
Sorry if I'm posting this in the wrong place but there is no forum dedicated to this phone. I'm guessing because it just came out this month.
Click to expand...
Click to collapse
where can i find these threads? can you point me to it... maybe i can try and find something, or do something different and help out with solving it.
EDIT: did these threads say for the MTQ or was it just a thread for a random 2.3.4 device?
The threads I saw were just for a random 2.3.4 device. I saw another thread on xda with someone trying to root this phone but just like this thread no one is answering.
Has anyone found any methods to root this phone?
Success!
After several attempts to root via SuperOneClick 2.2, I tried something totally random from another LG rooting thread that seems to have worked. Install ADB, then do:
WINDOWS> adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit
Then run SuperOneClick 2.2 and it should root properly.
I will have to give this a try on one of my Windows PC's. Linux and SuperOneClick are not playing nice together right now.
+1
Good Job Man....Worked for me. Have root and superuser.
Ditto! Root, & Superuser
== Instructions that worked for me ==
- Download myTouch Q drivers (Search "mytouch Q usb drivers" - Can't post links yet! XD )
- Check that adb recognizes device: C:\> adb devices
- Follow eamondaly's instructions:
WINDOWS> adb shell
$ echo 1 > /data/local/lge_adb.conf
$ exit
Click to expand...
Click to collapse
- Run SuperOneClick v2.2
- Wait for phone to reboot (SuperOneClick seems to be paused)
- Reset USB debugging (mine was turned off after reboot)
- Wait for SuperOneClick to finish.
- Enjoy rooted phone
Thanks
Okay thanks for the root methods greatly appreciated but now I am starting to get into developing anyone can teach me how to make a system dump to try and make my own roms I am a fast learner ort at least point me in right direction thanks again
Im not shure if im doing something wrong, i had better luck rooting an xperia play, a Droid X, and a htc mytouch, but this lg mytouch wont go for me. I tryed runing adb, i know how to use, was doing a little programming with it and eclipse. Anyhow, typed everything in and this is what my cmd shell looked like...
C:\ADB>adb shell
$ echo 1> /data/local/lge_adb.conf
echo 1> /data/local/lge_adb.conf
$ exit
exit
Then i tryed running superoneclick , tryed root and shell root, neither seem to work, it goes threw some and then hangs. my phone disconnects and reconects, thats it though. i checked in terminal, typed su, access is denied. i tryed it with debugging on and off, sd mounted and not.
Any ideas or tips. im using windows vista.
DMOYER said:
Im not shure if im doing something wrong, i had better luck rooting an xperia play, a Droid X, and a htc mytouch, but this lg mytouch wont go for me. I tryed runing adb, i know how to use, was doing a little programming with it and eclipse. Anyhow, typed everything in and this is what my cmd shell looked like...
C:\ADB>adb shell
$ echo 1> /data/local/lge_adb.conf
echo 1> /data/local/lge_adb.conf
$ exit
exit
Then i tryed running superoneclick , tryed root and shell root, neither seem to work, it goes threw some and then hangs. my phone disconnects and reconects, thats it though. i checked in terminal, typed su, access is denied. i tryed it with debugging on and off, sd mounted and not.
Any ideas or tips. im using windows vista.
Click to expand...
Click to collapse
you are running under admin right I know silly question but had to as lol
Thanks eamondaly
I just want to thank eamondaly for this method. I just ran superoneclick 2.3.1 and it worked perfectly. I don't know if it was your method that worked or if superoneclick 2.3.1 fixed it but all that matters is my phone is now rooted. Thanks.
Thanks a lot for the root method, I've been waiting patiently for this. Now can we get to making mods for this phone now?
Edit: Anyone having trouble sending/receiving MMS messages? I cant seem to send or receive them.
I was having an issue with receiving MMS on both my wife's and my phone. Ditching the stock messaging client and downloading Handcent resolved it for both.
Switching MMS apps didn't work. Tried a number of countless APN setups. I just decided to unroot and factory reset. Everything is working again.
titanium pro back up image
hey all,
Im sure this is a random spot for this but, since we dont have a home yet.
Im looking for a stock back up image (Titanium backup pro)with all apps and system settings. I think I may have cleared out a system file or two when cleaning out all the Tmo bloat.
Any help or other suggestions would be great.
I found another way to root easily. http://www.unlockroot.com download, install and click root. I had issues with superoneclick and the adb method but this gave me full root with superuser and now I am happy that all the t-mobile crapware is gone
I'm trying to root my T-Mobile MyTouch Q and not having any luck. It's Android 2.3.6, but I tried running "echo 1 > /data/local/lge_adb.conf" and I get a permission denied error. I tried SuperOneClick version 2.2 and 2.3.3. SuperOneClick gets to step 7 than hangs and nothing happens. It says waiting for device. I also tried Unlock Root and it fails to get shell root. I searched all over google and the xda forums, but all say to run that command then run SuperOneClick and that hasn't worked for me. Anyone have any ideas?
whats up guyz im new/old to this forums new/old means , i dont get online to much
well i have been tweaking a little bit with my droid DNA and found out some work around for some problems people might be having trying to unlock their bootloaders
the first problem i encountered was the adb killing process , adb is out of date . there is a little work around for this , that worked with me and my friend s DNAs to resolve this we just killed the adb daemon with this command
adb kill-server
then we started the server with the command
adb start-server
allright . the only way you will not get that error of adb out of date is , if you see adb starting on some port . i forgot the port number, but thats the only way you will not be getting the error ..
the second problem i encountered in the process of unlocking my phone was the restore update not finishing , which was caused by the bug of adb out of date error. once you resolve the problem with the adb bug out of date error , then you will be able to restore the phone successfully
but hold on , there is another problem some people might be getting , when you execute the command " adb restore backup.ab " if your device is taking to long to finish the restore and the window is behind looping, dont worry about it just wait couple of minutes control -c on the window looping and control -c on the window that you waiting on the restore to finish ... i tried that couple of times then i figure that the restore did go thru ..
some people might be getting an error with this command "adb shell mv /data/DxDrm /data/DxDrm_org" if you getting the error that says failed to blah blah blah permission denied , the cause for of that error is that the restore didnt go thru . if you got that error you can reboot safely , your device is not bricked yet lolz ..
when you get to the section that you have to repeat the exploit again , you gonna start getting the error again with the adb killing the process out of date thingy , dont worry just redo the work around i posted above , i control c the restore window and the loop window
couple of times just to make sure it was working fine , and it did . it was working fine
sorry for my english guys . i just wanted to point out those little flaws in the process of unlocking the bootloader , just in case some people get the same errors , they wont have to break their heads with it ... blessed be ..
Minor audible...
I was using the video made by DroidModderX and was able to get through it basically step by step with one minor hiccup. One the step where you start the first command prompt to do that "loop of errors" and move to the second command prompt, my system had an error doing this until I unplugged the phone and plugged in again. That wasn't mentioned in the tutorial but worked great once I did that part. It seemed like ADB got a little screwed up or something but, once I unplugged/ replugged it all worked normally. One other thing I noticed was that in the video (he uses a mac) the first command prompt continues to "loop" until you hit CRTL + C and on mine as soon as did the command in "prompt 2" the loop stopped on its own although all of the commands still worked as planned. I was doing this on Windows7 32bit. Hopefully that makes sense or is helpful to someone...
all you had to do was kill, then restart adb? that's not doing the trick for me, damn
EDIT: I got mine to work by uninstalling HTC Sync, it has an adb.exe file that was causing the error
I was able to leave HTC Sync installed but I had to uninstall Droid Explorer from my Incredible days. Only then did the ADB out of date error stop.
I used this before with HTC Sync. Maybe that is why I was able to keep it installed.
The attached zip is from http://visualgdb.com/adbfix/
when i try to boot insecure.img it says cannot load "insecure.img" : no error
placed insecure.img in the root path (where i installed adb C:\Android)
but my device is detected by cmd "fastboot devices"
also installe HTCSync 3.0.0.007
also in Windows device manager i can see "my htc"
whats wrong?
anyone can help me
my device is "unlocked" and s-off
if i remember correctly - all the htc sync stuff should be turned off completely (through the task manager)
look here:
http://forum.xda-developers.com/showthread.php?t=1416896
guru_shastri said:
if i remember correctly - all the htc sync stuff should be turned off completely (through the task manager)
look here:
http://forum.xda-developers.com/showthread.php?t=1416896
Click to expand...
Click to collapse
htc sync is turned off bytheway cant connect tablet via sync(htcsync can not find device is problem?)
but by fastboot devices cmd is listed
and in widows 7 device manager
still didnt load insecure.img
Iv installed new htcsync correctly find my Device then i turned off htcsync pc antyvirus windows firewall
and try to root it reboot in bootloader but it still cant load insecure.img(is in root folder where adb rooted and added in "invironment var." path C:\Android)
I have :
1. adb&fastboot (11MB) extracted from sdk(downloaded work good & root in C:\Android)
2. JETSTREAM-DooMLoRD-insecure-kernel-autoroot-test2-boot.img(renamed insecure.img and copy to C:\Android )
3. DooMLoRD_v2_ROOT-busybox-su
4. htc driver (find in fastbootdevices cmd and htcsync)
5. usb debbug mode
is that enough for rooting?
help please
did u make sure all the adb processes in the background are closed?
guru_shastri said:
did u make sure all the adb processes in the background are closed?
Click to expand...
Click to collapse
thanks for replying
how can i be sure is not running in background by taskmanager?
usually i use adb once and fresh to avoid interfering
i dont think thats problem bytheway i test again
can device b s-0ff without rooting?
in my device is so! (s-off unlocked but not rooted)
another Q can use wifixmanager to fix wifi problem when using another SIMprovider(not AT&T sim)
i'm having hard time figuring out the problem. you can't get root access?
can you post a picture of what happens when you try?(printscreen)
as for the s-off, i'v heard of one other device that was shipped s-off from HTC, but that's it. u might be the second one.
guru_shastri said:
i'm having hard time figuring out the problem. you can't get root access?
can you post a picture of what happens when you try?(printscreen)
as for the s-off, i'v heard of one other device that was shipped s-off from HTC, but that's it. u might be the second one.
Click to expand...
Click to collapse
i didnt buy it directly from origin shop ,seller unlocked it but i dont know he s-off it or not
no need to screen shot its simple what happennig
just :
Run \ cmd \ adb reboot bootloader(device rebooted in white screen above "unlocked" in secound line "s-off")
\ fastboot devices(devices is listed successfully) \ fastboot boot filename.img
and it says
" cannot load "insecure.img" : no error "
when try using titanum or ram manager it say device not rooted and cant access root directory in file explorer
just it, and more try will not successfull
i try a fresh adb (sure no adb running in background) as u said but no ghange
maybe any change by seller caused problem?
Try fastboot boot insecure.img
The filename should be same as what the insecure kernel's name is. So putting filename.img might be the problem. They should correspond.
Sent from my HTC One using xda premium
kailashpchhabria said:
Try fastboot boot insecure.img
The filename should be same as what the insecure kernel's name is. So putting filename.img might be the problem. They should correspond.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I know exactly did that :
as i said in earlier post
JETSTREAM-DooMLoRD-insecure-kernel-autoroot-test2-boot.img(renamed insecure.img and copy to C:\Android )
(drive c is primary drive that Win7 is intstalled in)
but still it say:
" cannot load "insecure.img" : no error "
its seems no one can haelp me:crying:
maybe the file is corrupt?
try this:
https://dl.dropboxusercontent.com/u...MLoRD-insecure-kernel-autoroot-test2-boot.img
also, you need to search other devices forums. this forum is pretty dead, and i'm pretty sure an issue like that occurred elsewhere as well
guru_shastri said:
maybe the file is corrupt?
try this:
https://dl.dropboxusercontent.com/u...MLoRD-insecure-kernel-autoroot-test2-boot.img
also, you need to search other devices forums. this forum is pretty dead, and i'm pretty sure an issue like that occurred elsewhere as well
Click to expand...
Click to collapse
thanks for uploading file
i test new insecure but same problem:
" cannot load "insecure.img" : no error "
Please Help
mamalypro said:
thanks for uploading file
i test new insecure but same problem:
" cannot load "insecure.img" : no error "
Click to expand...
Click to collapse
Please l'm new member here I want to root my jetstream but i didn't find the files any where all links are currupted so could you please please please upload the files for me insecure kernel and root toolkit thank you very much
heres what u want threre is two link in middle of page
http://forum.xda-developers.com/showthread.php?t=1416145&page=6
DooMLoRD_v2_ROOT-busybox-su.zip - [Click for QR Code] : http://forum.xda-developers.com/attachment.php?attachmentid=901243&d=1329199186
JETSTREAM-DooMLoRD-insecure-kernel-autoroot-test2-boot.img : http://forum.xda-developers.com/attachment.php?attachmentid=901244&d=1329199186
downoad and enjoy!
and say what happend
i have a Conquest and something happened the other day. I enabled su at boot and POOF it reset and got stuck on a bootloop. i can get into the stock recovery menu though. Every time i try to use ADB to push/install/sideload any zip files i see this on my screen
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted
i made a backup of everything using TitaniumBackup but i have absolutely no idea what i am supposed to do now. i have read and read everything pertionent to my issue and have found no fixes for this. i cannot do anything with the bootloader at this time because the forums are all vague to the content towards Alcatel devices. the bootloader i have is
L4CCY0Y0BQ00
model Alcatel 7046T
manufacturer/brand TCL
Radio: MSM8916
when i view recovery logs everything i see has 0 at the end so i assume its disabled. and i mean EVERYTHING.
i can send a copy of the TitaniumBackup zip file to someone who can help me with this issue. i have the stock recovery also. i am at my wits end at the moment. would someone please help me with this issue and possibly run me through some steps as to what i can do to get this phone successfully working again? I have never had this much trouble with a phone/tab as i am with this one. i am really desperate as i cannot afford to buy a new phone nor do i want to send it in to boostmobile to have the "look" at it. they will laugh at me and say "warranty void".
info from the rec log
I:Got arguments from boot message
locale is [(null)]
stage is [ ]
reason is [(null)]
cant open /dev/tty0: no such file or directory
fb0 reports (possibly inaccurate)
v.bits_per_pixel = 32
vi.red.offset =0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length =8
framebuffer: 0 (720x1280)
found frames = 7
libpng warning: Not recognizing Known sRGB profile that has been edited
Command: "recovery" "--show_text"
then i am assuming it is showing my build.prop information i would post it here but thats alot of typing for me. i really need help. please. i normally dont ask for help i just fix it but i cant this time.
same issue!!
im having the same issue with my friends phone....i rooted it with king root and used supersu me to delete kingroot and install supersu me, and when i "successfully" updated the binary with the newly installed supersu it told me to reboot...i clicked the " reboot" option given by supersu it went to reboot but just stays at the loading screen where it says android and alcatel one touch.
where are you getting these packages you are trying to install with adb ?
i wanna try that too but i woulod rather just use odin to flash the stock rom back onto it, but i cant find the stock rom file anywhere , im assuming because this phone is new ( released july 2015)
can anyone hook me up with the stock rom file for alcatel onetouch conquest 7046t boost mobile???
Could you please upload the stock zip you have.
sosthenisRR said:
i have a Conquest and something happened the other day. I enabled su at boot and POOF it reset and got stuck on a bootloop. i can get into the stock recovery menu though. Every time i try to use ADB to push/install/sideload any zip files i see this on my screen
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted
i made a backup of everything using TitaniumBackup but i have absolutely no idea what i am supposed to do now. i have read and read everything pertionent to my issue and have found no fixes for this. i cannot do anything with the bootloader at this time because the forums are all vague to the content towards Alcatel devices. the bootloader i have is
L4CCY0Y0BQ00
model Alcatel 7046T
manufacturer/brand TCL
Radio: MSM8916
when i view recovery logs everything i see has 0 at the end so i assume its disabled. and i mean EVERYTHING.
i can send a copy of the TitaniumBackup zip file to someone who can help me with this issue. i have the stock recovery also. i am at my wits end at the moment. would someone please help me with this issue and possibly run me through some steps as to what i can do to get this phone successfully working again? I have never had this much trouble with a phone/tab as i am with this one. i am really desperate as i cannot afford to buy a new phone nor do i want to send it in to boostmobile to have the "look" at it. they will laugh at me and say "warranty void".
info from the rec log
I:Got arguments from boot message
locale is [(null)]
stage is [ ]
reason is [(null)]
cant open /dev/tty0: no such file or directory
fb0 reports (possibly inaccurate)
v.bits_per_pixel = 32
vi.red.offset =0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length =8
framebuffer: 0 (720x1280)
found frames = 7
libpng warning: Not recognizing Known sRGB profile that has been edited
Command: "recovery" "--show_text"
then i am assuming it is showing my build.prop information i would post it here but thats alot of typing for me. i really need help. please. i normally dont ask for help i just fix it but i cant this time.
Click to expand...
Click to collapse
You can try to rename the file to "update.zip" and install it that way. It would be best to put the zip on the internal sd if possible, I believe. Also the error you are getting appears to be a signature/oem issue. You could also try editing the zip you have through the meta/google/??? not sure if this is correct folder. You should be able to search on XDA for modifying custom/stock rom. I believe you have to delete or add a few lines in a script file. Needless to say I have the same issue but no access to stock rom. Hope this helps. Please share the zip you have and I will post any results I have witgh my head ache. BTW im not positive, but believe this issue could be a result of a locked boot loader.
---------- Post added at 11:54 PM ---------- Previous post was at 11:46 PM ----------
Another thing you might try is to install via fastboot
"fastboot flash system filename.img" you will have to convert zip.
Alternatively, you could try "fastboot flash zip filename.zip"
Not sure if you can flash tar files this waym but this may be an option also. Using fastboot should eliminate the errors you have described in your post.
---------- Post added at 11:59 PM ---------- Previous post was at 11:54 PM ----------
Another thing you might try is to install via fastboot
"fastboot flash system filename.img" you will have to convert zip.
Alternatively, you could try "fastboot flash zip filename.zip"
Not sure if you can flash tar files this waym but this may be an option also. Using fastboot should eliminate the errors you have described in your post.
all of this seemed good to be honest but did not work on my device. it seems that i do not have the stock recovery i believe as it says in the first few lines of the recovery log that TZDATA is looking for info from Los Angeles and also from a file made in 1970. i video recorded it so i could read it in .25x speed. it was a pain. could anyone use MTK Droid tools to get their recovery and scatter files also with the rom itself so that i may fix this. the device registers as MTK (Media Tek) for some reason. maybe because it was manufactured in China and most Chinese devices run through MTK as a primary then through their subsidary. if anyone c ould try this for me and post their findings i would greatly appreciate it. i am running trough all my ideas at the moment. Thanks guys.
gonna try a new approach i guess.
Has anyone had any further developments on this device? I have even tried to find another one at Boost Mobile but according to the clerk they were sold out across the nation which i find hard to believe. I am sending the device in for the warranty which a representative said they cover just about everything programming wise no matter what really so ill try that next week. Wish me luck everyone. Tnx.
i have the phone in perfect condition. i have hesitated rooting it. Going by the comments i have seen so far most people have either bricked their devices and are not able to get back to stock. i want to use the device with a GSM simcard its only has options for LTE and CDMA. Is it possible like to activate the GSM bands on this phone
Retracted
sosthenisRR said:
Has anyone had any further developments on this device? I have even tried to find another one at Boost Mobile but according to the clerk they were sold out across the nation which i find hard to believe. I am sending the device in for the warranty which a representative said they cover just about everything programming wise no matter what really so ill try that next week. Wish me luck everyone. Tnx.
Click to expand...
Click to collapse
I believe this phone uses the Qualcomm chip set. Mtk based methods wouldn't work with those right?
New info
So I've done some research into the boot loader, and from what I've found, traditional rooting methods will not work. Fastboot it seems is disabled on the device and won't accept any fastboot commands. The only program I've seem successfully unlock the boot loader is Sigma Key, which costs a good deal of money( for those prices you could rebut the phone). I do have a question though, if I got hold of a factory version of the stock ROM, could I reflash it with the boot loader being locked?