Hello! So after some research in the forum, and seeing that it can be "easy" to root your phone, even with a locked bootloader, I decided to look into doing this with my Verizon Galaxy Note II to get familiar with custom ROMs. I had been running on 4.1.2
Please redirect me to relevant forum information for DIY or feel free to contribute any help below. Also, feel free to shame me for not finding it myself, as I couldn't find it myself.
I used "NoYouVerizon-GalaxyNote2-Casual R515" to root my phone and about 5-10 seconds through the installation it errored out and showed "Disconnected". It stated that I needed the relevant drivers from Adam Outlet which I accepted to download, but I did not re-recognize my phone afterwards while in the download screen. But, since it error, I get the incompatible firmware yellow triangle of frustration. I can't seem to use any software such as Odin, most likely because my bootloader is still locked?, so I'm going to ask you experts for help while I research a way to get it out of this mode.
Edit: Also, I have the issue where Odin states "Can't open the serial(COM) port" which causes a failure. Attempted to flash root66_VZW_Stock_etc
Edit2: Was a Samsung Kies issue. Uninstalled and able to start root66 on Odin. Processing now
Edit3: Was able to wipe/reboot in recovery mode to get back to stock. Now I'm curious of why Casual had the error. Any suggestions from the error file uploaded?
Edit 4: I have my phone back up and working with root access. Though I'm unsure how I have root access without doing much to unlock the bootloader from verizon, I guess this works. Any commentary welcome.
Any help would sincerely, 100% be appreciated!
Related
Okay, So I've been looking since August for a rooting tutorial for this phone and I've had zero luck.
I've attempted nearly every simple method of rooting (Gingerbreak, Superoneclick, etc) and all to no avail.
My phone has been in debugging mode and I do have the drivers installed (courtesy of the Huawei's website) so I'm not sure where to go from here.
I've learned that holding down the Power Button and the Volume Up button boots the phone into Recovery mode but I'm not sure if that's helpful or what to do with it. I considered attempting to use Odin but I can't find out how to get my phone into Download Mode (if it even has it).
If anyone could guide me of where to go or what to try, that would be greatly appreciated. I'll answer any questions that you need.
It's running 2.3.6 gingerbread, and the cell provider is Cricket, if anyone needed to know.
Huawei doesn't have the phone listed in phones that need the bootloader unlocked.
I've also found one tutorial, but it doesn't work, I keep getting permission denied on "adb push root/flash_image /data/local/", and it also uses Z4 and from what I've read, Z4 doesn't work on devices past 2.2, I could be wrong though.
Please help me, I'm a tad desperate.
Did you figure this out? ....or somebody did? Thanks.
I'll start out that I'm new to android, been an avid blackberry user that just purchased my note 2. I followed the casual root application, and unlocked and rooted my device. I went to install cm 10.2 mod on my device after wiping the device in development mode and it failed. Now my device will not respond to either download mode or development mode. I'm kind of stuck and not sure how to approach the correct solution to get my device back up and running.
Any help would be very appreciated, Thanks in advanced!
Sorry I should of mentioned this in the above post, I did make sure that the cm mod I downloaded was for my specific device. Is it possible that maybe the root/unlock method failed and thats where I went wrong when installing the cm mod? I also get no response when the device is plugged into my pc. So its not being read by odin currrently
Since it appears I have hard bricked my device, not quite sure what steps I can do to recover. I get no power to the device in any situation, I've read online about riff jtag (sorry spelling), if anyone could point me in a direction it would be helpful. Thanks in advance.
Hi everyone,
This may be a challenge for smart phone genius' out there (kudos to the clever person that can help me). Here is the scenario... I bought a new smart phone from Wallmart a few weeks ago (SAMSUNG model SM-G550T2). Yesterday, I decided to try to root it. I was able to root it successfully (no problems yet). Later, (after I had messed with the settings, like a dumb noob) I rebooted the phone and I get "Custom binary blocked by FRP lock" and of course it won't start. So, that said, I started scanning the internet for a way to fix this (and at first I was encouraged by all the info). Here is what I have, unsuccessfully, tried. Installed the Kies3 program on 2 different PCs. Both said that my phone was not compatible. BTW, I tried the original Kies program also and it would not connect. ODIN worked fine but I could not locate an image file of the stock firmware for this phone (maybe it's too new, I don't know). I can get the phone into DOWLOAD mode but not RECOVERY mode. If someone can help I will be eternally greatful.
YouTube on 5 stock firmware link plus manual and link to USB driver and Odin. under YouTube name rootandriodz. he even has a ROM tutorial. Im sure there are other postings as well. just in case you dont trust the first one you see. good luck, i have the same phone..
I'll try to get as straight tot he point as possible.
Been using my Mobile one touch pix 7 for a little over a year and always installed Ota updates. Well I rooted the tablet not too long ago, forgot which method I used, but was working fine.
an Ota update came through and totally forgot it was rooted, and tried to install it, at which point the whole tablet got bricked.
It ended up in recovery, and I selected due to failure, to format and wipe the data.
Anyhow, The unit will stay at the boot screen for a while then show command error and then show the recovery screen, my only options are:
reboot
update from sd card
update via adb
update via memory
reboot Bootloader
power off
Well I've tried updating by downloading system images via adb, they return a verification error.
I've tried using adb side load to try to install an Ota update file I found for it, returns a verification error.
I cannot get into download mode, fast boot mode I think does not work as windows reports 3 android devices, but the mobile update software cannot see anything, and fast boot gets stuck at waiting for devices.
I suspect the tablet is for lack of a better description totally bricked and just a paperweight.
I am at a loss of what to try from this point. I'm sure wiping the data after the failed update killed it completely but not sure.
Anyone have any guidance here? I've downloaded a few images from the web I found that say they are for this tablet model, but still getting verification error.
Is there any flashing software I can get that may be able to access the tablet or can I copy a file to the scared and have it try to run an update from there. I don't care if it is rooted or not, just want to get it usable again.
I can run Mac OS, windows 10, windows 7, windows xp, or even have no issue getting a linux version going, whatever will work best for this I can use it. windows 10 I was able to manually add the drivers but windows 7 is not letting me do it the same way. I can connect via adb sideload only, no other adb functions seem to work.
I'm not a total news when it comes to custom rooms, as I have done it with another tablet, and an android car radio, but those were pretty straight forward and bootable so never ran into a brick issue yet.
I have a feeling this is toast and I hope that is not the case.
If anyone here can help out, I would appreciate it.
Thanks again....
Need help here to. Been searching with no luck. Any my issue is.
Rooted kingroot, flashed twrp with flashify and now I'm stuck on twrp. Been searching for any custom stock rom. I forgot to unlock the bootloader but I did enable usb debugging (i didn't see any oem options).
Any k 28532Jonsunf of help would be greatly appreciated.
This sorta happen to me. I rooted pixi 7 with kingroot, and was able to delete a lot of bloatware. However, when I was using lucky patcher it pretty much messed up the play store. But it was fine. I could download stuff through the Internet. But sooner or later I needed to fix it. Tryed a lot of ways but it didn't help. So I factory reset the tabletand now im stuck at the Setup Wizard. It just won't let me let me through. I thought its was over, but then I get a message saying there is an update available. So I download it and installed it. But all I get at the end is error. So now I need to flash it with stock. I tried the img. too, but it doesnt show up in the recover menu. If you found a solution please tell me
Can anyoonneee help me find a good Custom Rom for the alcatel one touch pixi 7 (9006W)? Sucks that there's not much info for this device (probably cause the device sucks lol) I'm running on lollipop 5.0.2 and am not able to get OTA update due to rooting. Unrooting didn't help. It seems only answer is custom rom but don't want to risk bricking it as I don't have a computer at home. Also, I am new to this so if anyone can share some insight, I'd be eternally grateful
P.s
It's a t mobile device but I only use it on wifi.
Am using kingroot.
Have never installed a custom rom
****ing device is 8 gigs. 1 gig Ram.
Is it possible to get Nougat?
Help meeee lol
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!